Skip to main content
Glama

Gate Session Stats

gate_session_stats

Reports measured file, byte, and token work plus deduplication cache activity for the current session; pass a project root to include persistent cache totals.

Instructions

Measured file/byte/token work plus dedup cache activity. See gate_help gate_session_stats.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gate_session_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectRootNoOptional project root for persistent cache totals (same as gate_compress_file).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.12

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses no behavioral traits such as whether the call is read-only, whether it mutates the cache, or what it returns. 'Dedup cache activity' hints that cache state is involved but never clarifies whether reading it affects anything.

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?

Two short sentences with the substantive content front-loaded and zero padding. The second sentence is a pure deferral, but it costs little space.

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 should convey what a caller gets back, and it only gestures at counters plus cache activity before redirecting to gate_help. For a simple zero-required-parameter stats tool this is passable but leaves an agent guessing at the return shape.

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

Parameters3/5

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

The single parameter has 100% schema description coverage, and the description adds no meaning beyond the schema's explanation of projectRoot as a persistent-cache root. Baseline 3 applies since the schema does the work.

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

Purpose3/5

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

The description names the content reported (file/byte/token work plus dedup cache activity), which tells an agent this is a session statistics reader rather than a mutation, but there is no explicit verb and the title 'Gate Session Stats' merely restates the name. It hints at differentiation from gate_compress_file and gate_graph_query without clearly stating it.

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?

The only guidance is 'See gate_help gate_session_stats,' which defers the decision rather than explaining when to call this versus siblings like gate_compress_file. There is no condition, prerequisite, or alternative named.

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