Skip to main content
Glama

studio_progress

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Report progress on your own game's active studio request and renew its 30-minute lease.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>",
      "note": "<note>"
    },
    "name": "studio_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
requestYesRequest id from studio_wait.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the auth requirement (OAuth connection or Bearer API key) and the 30-minute lease that this call renews, which explains the declared idempotentHint=false and gives an agent a real reason to call it periodically. It still doesn't say what the response contains or what failure looks like when the lease has expired.

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 sentences, both load-bearing: auth prerequisites first, then the operation and its side effect. No filler, no restatement of the name, and the most decision-relevant constraint (sign-in) is front-loaded.

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

Completeness3/5

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

There is no output schema, so the description must be sufficient on its own; it covers what the call does and its lease semantics but says nothing about the progress note's role or what a successful call returns. Adequate for a small two-parameter tool, but with visible gaps.

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

Parameters2/5

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

Schema coverage is 50%: the 'request' parameter is already documented as coming from studio_wait, so the description adds nothing there, and the required 'note' parameter (a 1-1000 character message) is never mentioned in the description at all. With only half the parameters described in the schema, the description needed to compensate and does not.

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 and resource: 'Report progress on your own game's active studio request,' plus a secondary effect (lease renewal). It scopes the operation to the caller's own game, which separates it from broader change-tracking tools, though it never names its closest siblings (studio_done, studio_fail).

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 context is implied rather than stated: the request id comes from studio_wait, so an agent can infer this is the follow-up call while work is still in flight. There is no explicit when-not guidance, no mention of when to prefer studio_done or studio_fail instead, and no statement about what happens if the lease already lapsed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources