Fetch the complete tutoring context for a session in one call, including mastery estimation, prerequisite checks, and assessment data, to reduce round trips.
Return the full teaching context in one call to reduce round trips.
| Name | Required | Description | Default |
|---|---|---|---|
| node_id | No | ||
| session_id | Yes |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It only says the tool returns context; it doesn't state whether the call is read-only, what 'full teaching context' includes, how node_id affects the result, or what happens with invalid session_id.
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 sentence that is front-loaded with the action and the resource. The phrase 'to reduce round trips' is slightly redundant with 'in one call', but the description is compact and readable.
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 tool promising 'full teaching context', the description doesn't specify what that context contains, how node_id scopes it, or what the response looks like. With no output schema or annotations, an agent cannot predict the result shape or distinguish this from other getters, making the definition incomplete.
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%, and the description adds no meaning for session_id or node_id. The parameter names hint that session_id selects a session and node_id may scope to a node, but their effects on the returned context are unexplained, so the description does not compensate for the schema gap.
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 clear action ('Return') and resource ('full teaching context'), and adds the aggregation benefit of reducing round trips. The term 'teaching context' is not defined, and the description doesn't differentiate it from narrower sibling getters like get_session_info, but the core purpose is recognizable.
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?
Provides no explicit when-to-use guidance or comparison with sibling tools. The phrase 'reduce round trips' implies a bulk-read use case, but it doesn't state when to prefer this tool over alternatives like get_session_info or get_review_state, nor when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.