Skip to main content
Glama

What a session did

session_summary
Read-onlyIdempotent

Retrieve a single coding session's summary—title, status, branch, cost, tokens, turns, tool calls, touched files, and opened pull requests—using its session ID.

Instructions

One session: its title and description, status, branch, cost and tokens, turns and tool calls, the files it touched and the pull requests it opened.

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": "session_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesThe session's id, from recent_sessions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and mutability are covered. What the description adds is the return payload, enumerating cost, tokens, turns, tool calls, touched files and opened PRs — genuinely useful given there is no output schema. It stops short of noting behavior for an unknown or missing session_id, which a 5 would require.

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

Conciseness5/5

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

A single sentence with zero filler, leading with the scope ('One session') before enumerating contents. Every clause carries information an agent cannot get from the structured fields.

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

Completeness4/5

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

For a one-parameter read tool with full schema coverage, rich annotations and no output schema, the description is nearly complete — it effectively serves as the return-value documentation. The remaining gaps are the absence of any not-found or error behavior and no routing to the sibling that supplies the session_id.

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?

Schema description coverage is 100% and the single parameter is documented there, including its provenance ('from recent_sessions'), so the baseline of 3 applies. The description says nothing about the identifier's format or what happens on an invalid id, adding no meaning beyond the schema.

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 is a field inventory ('title and description, status, branch, cost and tokens, turns and tool calls, files, pull requests') for a single session, which makes the resource and its scope unambiguous even though no verb like 'retrieve' or 'fetch' is used. It does not explicitly contrast itself with siblings such as recent_sessions or next_session_handoff, so it sits at 4 rather than 5.

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 guidance at all — nothing says this is the drill-down after listing sessions via recent_sessions, nor how it differs from session_prose, cost, or next_session_handoff, which clearly overlap. The only hint about the entry point lives in the schema's parameter description, not in the tool description.

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