Track an ELSTER session by returning its current status, progress log, and screenshot path so you can monitor form-filling or check workflows started via the start tools.
Returns the current status, progress log, and any screenshot path for a session started via elster_ustva_start / elster_eur_start / elster_est_start.
| Name | Required | Description | Default |
|---|---|---|---|
| sessionId | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Only lists outputs (status, progress log, screenshot path) without disclosing whether the tool is read-only, requires authentication, or what happens on invalid sessionId. Minimal behavioral insight.
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?
Single sentence, front-loaded with verb and outputs, zero extraneous words. Ideal conciseness for a simple status-check tool.
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?
Tool is simple (1 param, no output schema), but description omits return value details (e.g., status codes, progress log structure) and does not compensate for missing schema documentation. Adequate but not thorough.
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% with no description for sessionId. Description adds no meaning beyond the schema, failing to clarify format, constraints, or purpose of the single parameter.
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?
Description uses specific verb 'Returns' and names three resources: status, progress log, screenshot path. It explicitly links to sibling start tools (elster_ustva_start, etc.), distinguishing from listing or cancellation tools.
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?
Implies usage after starting a session via named tools, but lacks explicit guidance on when to use versus alternatives like elster_session_list or elster_session_cancel. No when-not-to-use conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.