Skip to main content
Glama

style_status

Read-onlyIdempotent

Check the progress, current step, elapsed and remaining time, tokens, and errors of a style build or fix job; optionally clear a finished job from the app.

Instructions

How the style build or fix (make_style, fix_style, continue_style) is going: status (running, done, failed, cancelled), step and its name, what Claude does right now, minutes so far and left (a rough guess), tokens, errors and problems. Read-only unless close: true, which clears a finished job from Dinoctor's screen. When done, use_style switches to it and rate_style records how it went; when failed with canContinue, use continue_style. To stop it, use cancel_style.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "style_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
closeNoClear a finished, failed or cancelled job from Dinoctor's screen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations it discloses the meaning of each status value, flags that 'minutes left' is a rough guess, exposes errors/problems and a canContinue signal, and calls out the one mutating path (close: true clears a finished job from the screen). The annotations declare readOnlyHint=true unconditionally, so the 'unless close: true' clause usefully sharpens rather than repeats them, though it leaves a mild tension with the read-only claim that could have been stated more explicitly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The response payload is front-loaded in the first sentence, and the side-effect caveat and follow-up routing come after in logical order. It is dense and somewhat comma-spliced, but no sentence is filler; a slight restructure would improve scannability without adding length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-shape burden and does so by listing the fields an agent will see, plus the follow-up tools for each terminal state. Minor gaps remain: it doesn't say what the payload looks like when no job exists, and canContinue's location/shape is only implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter with 100% schema description coverage, so the schema already documents `close` fully. The description restates it ('clears a finished job from Dinoctor's screen') and adds the read-only-unless framing, but no additional nuance such as what happens if close is passed while the job is still running. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource (the style build or fix job produced by make_style, fix_style, continue_style) and enumerates what is reported: status values (running, done, failed, cancelled), step and step name, current activity, elapsed and remaining minutes, tokens, errors. That is specific enough to separate it from status, render_status and picture_status without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing for each outcome: when done, follow with use_style and rate_style; when failed with canContinue, follow with continue_style; to stop it, use cancel_style. It also states this tool does not stop or advance the job itself, which is the main misuse an agent could make.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.