Check JANCTION Render connection details, GPU worker availability, queue length, and API key usage before rendering or when jobs stall.
Show the JANCTION Render connection: server URL, whether GPU workers are online, queue length, and this key's usage. Call this if renders seem stuck or before the first render.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the disclosure burden alone. It implies a read-only diagnostic (no mutation hinted) and names the data returned, but does not state read-only-ness, auth requirements, or rate limits explicitly.
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 sentences, front-loaded with what it shows and followed by when to call. Every clause earns its place with zero filler.
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?
An output schema exists, so return-value explanation is unnecessary, and zero-param simplicity keeps the burden low. The only gap is the unexplained boundary with the sibling render_status.
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?
Zero parameters, so the baseline is 4. No parameter information is needed or missing, and the description correctly describes a no-arg diagnostic call.
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?
Specific verb 'Show' and resource 'JANCTION Render connection', with concrete fields (server URL, GPU worker status, queue length, key usage). It distinguishes itself from render_status by the connection/diagnostic framing, though the overlap with render_status is not explicitly addressed.
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?
Gives two concrete triggering conditions ('if renders seem stuck' and 'before the first render'). It doesn't explicitly contrast with sibling render_status, which is the nearest-overlap tool, so it stops short of a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.