Lists interactive Kratos Multiphysics sessions newest first, optionally filtered by state (starting, ready, closed, dead, lost) to track simulation runs.
List interactive sessions (newest first), optionally filtered by state: starting/ready/closed/dead/lost. 'lost' means the session belonged to a previous server process.
| Name | Required | Description | Default |
|---|---|---|---|
| state | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.9.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses newest-first ordering and explains 'lost', but omits whether the call is read-only, permission requirements, or how active sessions are treated.
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 tight sentences, front-loaded with the action and ordering. Every clause adds value, and there is no repetition of structured fields.
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?
This is a low-complexity list tool with an output schema, so return values need not be described. The description covers filtering and ordering adequately, though it could clarify the relationship to session_status for complete routing.
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 sole state parameter has no enum in the schema. The description compensates by enumerating valid states (starting/ready/closed/dead/lost) and explaining the non-obvious 'lost' value.
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 specific verb (List) and resource (interactive sessions), plus ordering (newest first) and an optional filter. It does not name any sibling alternative, but the purpose is unambiguous.
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 filter options but no explicit when-to-use versus session_status or session_start, and no exclusions. Usage is implied by 'List interactive sessions' rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.