Fetch status and details for a specific code execution session by providing its session ID. Use it to inspect or debug sessions created by the code interpreter.
Get information about a specific session
| Name | Required | Description | Default |
|---|---|---|---|
| sessionId | Yes | The session ID to query |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of disclosing behavior. The verb 'Get' indicates a read-only operation, which is useful context, but the description does not disclose what happens for invalid or nonexistent session IDs, response format, or any side effects. It is sufficient for a simple getter but not richly transparent.
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?
The description is a single, short sentence with no wasted words. It is appropriately front-loaded but leans heavily on the tool name, adding only the qualifier 'information about a specific' to clarify scope. This is concise and effective, though not exemplary in adding unique value.
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?
The tool has only one parameter with full schema description and no output schema. The description provides minimal context about what 'information' will be returned, but for a straightforward get-by-ID tool this may be sufficient. Given the lack of annotations and output schema, slightly more detail about return contents or error behavior would improve completeness.
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?
The schema coverage is 100%, with sessionId described as 'The session ID to query'. The description adds no additional parameter semantics beyond the schema, so the baseline score of 3 applies. The tool name and description reinforce the parameter's role but do not provide extra meaning.
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?
The description clearly states the verb 'Get' and the resource 'information about a specific session', making the tool's purpose immediately understandable. It distinguishes from sibling tools like list_sessions by scoping to a specific session, though it does not explicitly name alternatives.
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 description implies the tool should be used when information about one particular session is needed, in contrast to listing all sessions or starting/stopping sessions. However, it provides no explicit guidance on when to prefer this over siblings or mention prerequisites like owning a session ID, leaving the agent to infer usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.