get_session_infoRetrieve metadata for a specific session without loading all its thoughts. Inspect session details by name for a lightweight overview of stored reasoning.
Get metadata about a specific session without loading all thoughts.
| Name | Required | Description | Default |
|---|---|---|---|
| sessionName | Yes | Session name (format: category:name:subcategory) |
Changes observed during successful MCP inspections.
v1.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It does disclose one genuine behavioral trait — that this is a lightweight lookup avoiding the cost of loading thoughts — but says nothing about permissions, failure behavior for a nonexistent session, or what 'metadata' actually contains.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with zero filler; the scope qualifier is placed where it does the most work.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read tool this is close to adequate, but with no output schema the description should hint at what metadata is returned, and it does not. An agent knows what it gets conceptually but not concretely.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 fully documented in the schema (including the category:name:subcategory format), so the baseline is 3. The description adds no parameter-level meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (get) and resource (session metadata) and adds a scoping qualifier ('without loading all thoughts') that implicitly distinguishes it from heavier siblings like view_session. It does not name an alternative explicitly, but the purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'without loading all thoughts' implies the use case (lightweight metadata lookup rather than full session inspection), which is a reasonable implied routing hint. However, it never names view_session or list_sessions as the alternatives, nor states prerequisites, so guidance is inferred rather than given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.