Skip to main content
Glama

status

Read-onlyIdempotent

Check if Dinoctor is open and read the project’s style, format, scene and shot counts, plus the on-screen shot ID and indexes. Returns an open:false note if the app is closed.

Instructions

Quick read-only check: is Dinoctor open, the project's style and format, how many scenes and shots, and which shot is on screen (id and indexes). Returns { open: false, note } when the app is closed. For every scene and shot, use get_project.

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": "status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered; the description adds the non-obvious degraded response shape '{ open: false, note }' when the app is closed, which is real behavioral context an agent needs to branch on. It stops short of describing anything about the healthy-path payload beyond the field list, so a 4 rather than a 5.

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

Conciseness5/5

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

Two compact sentences, each front-loaded with the most decision-relevant information: what it returns first, the closed-app fallback second, the routing hint last. There is no filler.

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 and no parameters, the description carries the return-value burden and does so at a useful summary level, including the important closed-app variant. Field-level detail of the open-path payload is only gestured at ('id and indexes'), which keeps it from a 5, but nothing needed to call it correctly is missing.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. No misleading parameter talk is present.

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 gives a specific verb and resource ('Quick read-only check') and enumerates exactly what is returned: open state, project style and format, counts of scenes and shots, and the current on-screen shot with id and indexes. It also explicitly distinguishes itself from the sibling get_project, so an agent can pick between them without opening either 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?

'Quick read-only check' scopes it to lightweight status polling, and the closing sentence states the alternative and the condition that selects it: 'For every scene and shot, use get_project.' The when-to-use and when-not-to-use cases are both explicit.

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