Skip to main content
Glama

Singing Pet

Get video status

get_video_status
Read-onlyIdempotent

Check whether a video has finished rendering. Status is pending, processing, completed or failed. When completed, video_url is a direct MP4 link. Poll roughly every 10 seconds; a render takes about a minute.

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": {
      "video_id": "<video_id>"
    },
    "name": "get_video_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYesVideo id returned by create_singing_video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description still adds real value beyond them: the four status values, what video_url contains on completion, expected latency, and recommended polling cadence. Minor gap: no mention of what happens on unknown/expired video_id or whether failed is terminal.

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?

Three short sentences, front-loaded with purpose, then state values, then polling guidance. Every sentence earns its place with zero filler.

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?

No output schema exists, so the description takes on the return contract and does so well: enumerates status values and explains the completed payload. Combined with 100% schema coverage on the single input, an agent has everything needed to call and interpret it.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter's description already ties video_id to create_singing_video, so the schema carries the parameter burden. The description adds meaning about the response (video_url is a direct MP4 link) but nothing further about the input parameter. Baseline 3 is appropriate.

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 ('Check whether a video has finished rendering') and implicitly scopes it as a follow-up to video creation, which the parameter description reinforces ('Video id returned by create_singing_video'). An agent can immediately tell this apart from create_singing_video, delete_video, or list_videos.

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?

Gives concrete operational guidance: poll roughly every 10 seconds and expect a render to take about a minute. That is a clear when/how-to-use signal. It stops short of naming alternatives or when-not-to-use conditions, which keeps it from a 5.

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