Skip to main content
Glama

studio_status

View locally registered projects, jobs, and manually reported account budgets to track production status. Confirms no live credits are claimed.

Instructions

View locally registered projects, jobs and manually reported account budgets; no live credits are claimed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does usefully disclose data provenance and freshness ('locally registered', 'manually reported', 'no live credits are claimed'), which is real behavioral context a schema cannot express. It does not state read-only safety explicitly, nor anything about staleness handling, permissions, or response shape.

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?

A single sentence with the resource list front-loaded and the important caveat appended after a semicolon. Every clause earns its place; nothing is padded or restated from the name.

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?

For a zero-argument status tool with no output schema and no annotations, the description covers the returned categories and the key limitation about credit data. Adding a sentence on output shape or read-only nature would close the remaining gap, but it is usable as written.

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 the schema cannot convey anything further and the baseline of 4 applies. The description adds no parameter-level confusion because none exists.

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?

States a specific verb (View) and enumerates the resources returned: locally registered projects, jobs, and manually reported account budgets. The 'locally registered' / 'no live credits' framing separates it from the mutation siblings (studio_update_balance, studio_register_account), though it does not name them.

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

Usage Guidelines3/5

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

Usage is implied: this is the read/inspection entry point for studio state, and the 'no live credits are claimed' caveat signals when the data is insufficient. However, it never explicitly says when to prefer it or which sibling to use when live credit or balance data is needed, so the agent must infer routing.

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