session_statusRetrieve the current status and runtime parameters of any intercepted session by ID, enabling you to monitor and troubleshoot active network traffic.
Get the detailed status and runtime parameters of a session by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| error | No | ||
| session | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not explicitly state that the operation is read-only, nor does it mention error handling, prerequisites, or effects. The verb 'Get' implies a read but does not disclose safety or side effects beyond that inference.
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, front-loaded sentence with no filler. It communicates the core action and resource efficiently, making it easy to parse.
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 is simple with one parameter and an output schema, so return values are covered. However, the description does not explain when to use this tool relative to session_list or other session-related siblings, nor does it define what a 'session' is in this context. It is adequate but leaves contextual gaps.
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 0%, so the description must compensate. It only says 'by ID', which merely restates the parameter name session_id. It does not explain what a session ID is, how to obtain it, its format, or any validation, leaving the agent with minimal additional 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 uses the specific verb 'Get' with the resource 'detailed status and runtime parameters of a session' and qualifies by ID. It clearly differentiates from session_list (likely a list of sessions) and flow detail tools by focusing on session status, so an agent can distinguish it without opening the schema.
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: if you have a session ID and need its detailed status, this is the tool. However, it does not explicitly state when not to use it or mention alternatives like session_list for listing sessions, so the agent must infer context from sibling names rather than receive direct guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.