Skip to main content
Glama

get_cache_summary

Read-only

Retrieve whole-chat, latest-call, and latest-prompt cache reuse metrics for a specified chat to monitor token savings and prompt-cache performance.

Instructions

Get whole-chat, latest-call and latest-prompt cache reuse for a specified chat.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "get_cache_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
session_idYesThe current chat ID. Never substitute another chat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the useful fact that results are reported at three granularities (whole-chat, latest-call, latest-prompt), but says nothing about whether cached data can be stale or must be refreshed first.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is appropriate for a narrow read tool. The trade-off is that the terse enumeration ('whole-chat, latest-call and latest-prompt') is compact jargon that is not unpacked.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing returns, and it only partially does so via the three scope labels. For a two-parameter metrics read tool this is marginally adequate, but the unexplained limit parameter and absent staleness/ordering notes leave real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: session_id is documented in the schema itself, while limit (default 500, max 2000) has no description anywhere. The description's phrase 'for a specified chat' restates session_id rather than illuminating it, and limit — which presumably paginates whatever is counted — is left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ('Get') with a specific resource ('cache reuse') and enumerates three aggregation scopes: whole-chat, latest-call, latest-prompt, scoped to 'a specified chat'. That makes the operation clear without opening the schema, though it never explicitly separates itself from the sibling get_cache_history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance; nothing tells the agent to prefer this over get_cache_history or whether refresh_cache_dashboard must run first. The word 'summary' implies an aggregate read rather than a history listing, but the agent must infer that from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.