{"version":"2.1.257","anchor":"get-context-usage-tool-call-gains-a-detail-parameter","canonical_anchor":"get-context-usage-tool-call-gains-a-detail-parameter","heading":"get_context_usage tool call gains a detail parameter","tier":"use","area":"Context Usage","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/get-context-usage-tool-call-gains-a-detail-parameter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### get_context_usage tool call gains a detail parameter\n\nget_context_usage takes a detail parameter, where summary answers without extra token-counting API calls.\n\nThe `get_context_usage` tool call now accepts an optional `detail` parameter of `'summary'` or `'full'`. `'full'` is the default and performs per-category token-count API calls, while `'summary'` answers from the last response's usage plus local estimates without extra API calls.\n\nThe internal `tool.call` hooks API, used by plugin- and skill-authored tool invocations, now also accepts an optional `consent` string, which is injected as a synthetic human-origin message into the session context before the tool call runs.\n\n- Area: Context Usage\n- Names: `detail`, `summary`, `full`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}