get_sessionRetrieve the complete state of a session, including classification, interview answers, and decisions made so far. Use it to review progress and resume a structured pre-coding workflow.
Fetch the full state of a session: classification, interview answers, and any decisions made so far.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the behavioral disclosure burden. 'Fetch' implies a read operation and the description lists the returned state categories. However, it does not state that the operation is side-effect-free, how missing or invalid sessions behave, or whether any state is modified.
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 conveys the action, scope, and return content with no wasted words. It is easy to scan and directly useful.
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 description names the major categories of returned data, which helps in the absence of an output schema. Still, it omits error behavior, explicit read-only assurance, and any indication of how the nested interview answers or decisions are shaped. Acceptable for a simple getter, but not fully complete.
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, session_id, but the schema provides no description and schema coverage is 0%. The tool description mentions 'a session' but never explains that session_id identifies the target session, where to obtain it, or any format expectations. The description does not compensate for the missing schema documentation.
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 immediately states a specific verb ('Fetch') and a specific resource ('full state of a session'), then clarifies the contents: classification, interview answers, and decisions. This clearly distinguishes it from sibling tools like list_sessions or start_session.
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?
No guidance is provided about when to use this tool versus alternatives such as list_sessions or answer_question. The retrieval intent is implied, but there is no explicit statement of use cases, exclusions, or which sibling to prefer for other needs.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.