Skip to main content
Glama

Kubeez

get_status

Read-onlyIdempotent

Scope: read:generations. Poll the status of ANY job — media generation, music generation, or audio separation — by id.

PRE-FETCH (mandatory on the FIRST poll of a session): resources/read kubeez://skills/polling — first-poll delays per media type, then every 5s.

Auto-dispatches: pass the id and the server figures out which kind of job it is. Optionally pass kind to skip the lookup.

Returns the merged shape: • kind ('media' | 'music' | 'separation') — what the id resolved to • status — 'pending' | 'processing' | 'completed' | 'failed' • outputs / songs / vocals_url+instrumental_url — depending on kind • error_message on failure

Output URLs are CDN/R2 only — never vendor temp links. Keep polling until status='completed' AND those URLs are non-null. To SHOW the user a finished image, call view_media(output_id) — never download the CDN URL yourself.

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": {
      "id": "<id>"
    },
    "name": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial behavior beyond them: a mandatory pre-fetch step, auto-dispatch of the job kind, CDN/R2-only URL guarantees, and failure reporting via error_message. This is the kind of operational context annotations cannot express.

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?

Front-loads the scope line, then the blocking pre-fetch requirement, then parameters, return shape, and polling/display rules. The bulleted return shape makes variant fields scannable, and no sentence is decorative.

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

Completeness5/5

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

Despite an output schema existing, the description usefully restates the merged shape across three job kinds and adds the polling termination rule, which an output schema alone would not convey. For a polling tool with an auto-dispatch behavior, nothing an agent needs 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?

Schema description coverage is 0%, so the description must compensate; it explains that id resolves to a job kind and that kind is optional and only there to 'skip the lookup'. That is meaningful added semantics, though the id's accepted format (media vs generation id) and the enum's empty-string default remain unstated.

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?

States a specific verb and resource with explicit scope: "Poll the status of ANY job — media generation, music generation, or audio separation — by id." It also clarifies how it differs from the nearby view_media tool (use view_media to show a finished image, never download the CDN URL), so an agent can place it among siblings without opening a 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?

Gives concrete when-to guidance (first poll of a session requires the kubeez://skills/polling resource read), the cadence (every 5s), and an explicit termination condition (keep polling until status='completed' AND URLs are non-null). It also routes the agent to view_media for display rather than downloading.

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