Skip to main content
Glama

ninerouter_video_status

Read-onlyIdempotent

Poll a submitted video job using the reference returned at submission to check progress and know when processing completes.

Instructions

Poll a video job with the job reference returned at submission.

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": {
      "job": "<job>"
    },
    "name": "ninerouter_video_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only that this polls a previously submitted job; it says nothing about whether the call blocks, whether repeated polls are rate-limited, or what statuses come back, which matters for a polling loop.

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?

A single front-loaded sentence with no filler, which is appropriate in size. It is efficient but borders on under-specification rather than being genuinely tight.

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

Completeness2/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 annotations about return values, the definition should tell the agent what a poll returns and how to interpret progress. Nested object parameters are also undocumented, so an agent cannot reliably construct the call or interpret results from this definition alone.

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 description coverage is 0% and the single parameter is a nested object with two required fields. The description hints that 'job' is the reference returned at submission, but leaves connection_id completely unexplained and gives no shape or format detail for either identifier.

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 ('Poll a video job') and ties the input to its origin ('the job reference returned at submission'), which lets an agent connect it to the video-generation siblings. It stops short of naming an alternative, but the lifecycle stage is unambiguous.

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

Usage Guidelines2/5

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

The only implied usage is 'use after submission,' with no guidance on polling cadence, how to recognize a terminal state, or when to stop polling versus re-submit. For a polling tool those are the core usage decisions, and they are absent.

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