Read a PCB design session’s derived state—stage map, artifacts, and progress—using a session ID, or omit it to inspect the most recently active session.
Read a design session's derived state (stage map, artifacts, ...).
With no session_id the most recently active session is used.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.6.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, but 'Read' clearly implies a non-mutating operation. The description adds the useful default-session behavior, but it does not explicitly confirm read-only safety or describe any constraints beyond the default selection rule.
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?
Two short sentences with no wasted language. The core read behavior is front-loaded, followed immediately by the default-session rule that affects invocation.
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 and has an output schema, so return-value details need not be in the description. Still, given the large family of session-related siblings, the description could better clarify what 'derived state' includes and when this differs from session report/log tools.
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 coverage is 0%, so the description must explain the single optional parameter, and it does: omitting session_id selects the most recently active session. It does not document the expected session_id format, but the behavioral meaning is otherwise clear.
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?
Uses a specific verb and resource: 'Read a design session's derived state,' with examples 'stage map, artifacts.' It is clearly a read-oriented status tool, though it does not explicitly distinguish itself from siblings like design_session_report or design_session_log.
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?
Explains the session_id default behavior, which implies its use for reading status without an explicit session reference. However, it does not state when to choose this tool over related session tools such as design_session_report, design_session_resume, or design_job_status.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.