Skip to main content
Glama

status

Read-only

Call this first to check running Blender apps: selector, mode, version, busy/modal state, and capabilities before driving a session.

Instructions

Running apps: selector ('name#pid'), mode, version, busy or not, whether a modal operator is running, capabilities. Call this first.

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real substance by disclosing that each app carries mode, version, busy state, modal-operator state, and capabilities, which tells the agent what it can gate on. It omits whether the call is expensive, how apps are ordered, or whether busy/modal states are live or polled snapshots.

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?

Every token carries information and there is no filler, which is the right length for a zero-argument status probe. The structure is a naked noun-phrase list without a main clause, and the most actionable sentence ('Call this first') is placed last rather than front-loaded.

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 burden of describing return content, and it does list the fields an agent would need. Minor gaps remain: it does not say whether results cover all scenes/instances or how to interpret the busy and modal flags when acting on them.

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

Parameters5/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 is high. The one syntactic detail it does give, the 'name#pid' selector format, is a return-value convention rather than an input, which is appropriate here.

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

Purpose4/5

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

The description identifies the resource precisely as the set of running apps and enumerates the reported fields (selector, mode, version, busy flag, modal operator state, capabilities), so an agent knows it is a runtime inventory/diagnostic read. It does not differentiate from the sibling 'generate_status', whose name invites exactly the confusion this description could have resolved.

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

Usage Guidelines4/5

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

'Call this first' gives an explicit sequencing rule that is genuinely useful for an agent orienting itself before other operations. There is no statement of when NOT to call it or what alternative to prefer if the call fails, so it stops short of full when/when-not guidance.

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