get_sessionRetrieve a session's manifest by id, including its included entries and any attached baseline, to inspect or debug recorded proxy traffic.
Return the manifest of a single session by id, including its included entries and any attached baseline.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Session id from list_sessions. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the return content (entries, attached baseline), but says nothing about auth needs, error behavior for missing ids, or output shape beyond a loose hint.
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 well-formed sentence with the resource and scope front-loaded and no filler. Every clause earns its place by describing the returned manifest.
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 read-only getter with full schema coverage, the description is nearly sufficient, and it compensates for the absent output schema by naming what the manifest contains. Minor gaps remain around failure/missing-id behavior, but nothing essential is missing.
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?
There is only one parameter and schema coverage is 100%; the schema already explains that 'id' is a 'Session id from list_sessions.' The description's 'by id' adds no syntax or format detail beyond that, so the baseline of 3 applies.
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 and resource ('Return the manifest of a single session by id') and even enumerates the payload ('included entries and any attached baseline'). It implicitly distinguishes itself from list_sessions by scoping to a single session, though it doesn't name the sibling explicitly.
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?
Usage is implied: fetch the full manifest of one session once you have an id. There is no explicit when/when-not guidance and no mention of alternatives like list_sessions or compare_sessions, leaving the agent to infer the boundary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.