Skip to main content
Glama

Check video status

kreavo_check_video_status
Read-onlyIdempotent

Check async video generation status. Automatically polls external providers. Params: task_id

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": {
      "task_id": "<task_id>"
    },
    "name": "kreavo_check_video_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so safety is covered and the description needs only add context. 'Automatically polls external providers' adds useful behavior information, but it is ambiguous — it is unclear whether a single call blocks until completion or returns the current state, which is the single most important behavioral fact here. The mention of polling external providers also sits in mild tension with openWorldHint=false.

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?

Three short front-loaded fragments with no padding, and the core purpose leads. The trailing 'Params: task_id' is dead weight that duplicates the schema, costing it a point.

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?

There is no output schema, so the description is the only place an agent can learn what a status check returns — pending/completed/failed states, a video URL, or error semantics — and none of that is present. For a polling tool with a 0%-documented parameter, this is a significant gap.

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% for the single task_id parameter, so the description must carry the meaning and it does not. 'Params: task_id' merely restates the schema; it never says where the task_id comes from (the generate_video response) or what form it takes, and there is no statement of what happens with an invalid or expired id.

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: 'Check async video generation status', which separates it from the image counterpart (kreavo_check_image_status) and from the generation siblings. It does not explicitly name those siblings, so it falls just short of a 5.

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?

'async video generation status' implies the tool is used after kreavo_generate_video / kreavo_generate_product_video returns a task, but this is left to inference. There is no explicit when-to-use, no statement about whether it must be called once or repeatedly, and no routing to kreavo_check_image_status for image tasks.

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