Skip to main content
Glama

Outil.io

Get video build

get_video_build
Read-only

État d’une fabrication de vidéo : progress, warnings, puis projectId, version, scenes et export (url du MP4) quand status=done. Interroger toutes les 15–30 s ; ne pas relancer une fabrication en cours.

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": {
      "buildId": "<buildId>"
    },
    "name": "get_video_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and the description adds real behavioral context consistent with that read-only profile: the returned fields and the fact that they evolve with status. It also introduces an operational hazard disclosure, warning the agent not to relaunch an in-progress build, plus a polling cadence. It does not describe failure or terminal error states, so not a 5.

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 compact sentences with no filler: the return contract is front-loaded, then the polling instruction and the prohibition. Every clause carries information an agent needs, with no repetition of the name or title.

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

Completeness4/5

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

With no output schema, the description carries the burden of explaining returns, and it does so by naming the fields and the status=done condition. For a single-parameter read tool with annotations, that is nearly complete; only error/incomplete status values and the origin of buildId are left unaddressed.

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 description coverage is 0% for the single required buildId parameter; the schema only declares type string, format uuid. The description never explains what buildId is or where it comes from (presumably the build-creation tool's output). It does partly compensate by describing the result set, but the parameter itself remains undocumented.

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?

The description states a specific resource and scope: the state of a video build, enumerating what is returned (progress, warnings, then projectId, version, scenes, export MP4 url once status=done). That is far more specific than the title, which merely restates the name. Sibling differentiation is only implicit, via the reference to relaunching a build, but the intent 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 Guidelines4/5

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

Gives concrete usage guidance: poll every 15-30 seconds, and the exclusion "ne pas relancer une fabrication en cours". That covers during-use cadence and one clear prohibition, which is strong. It does not name a sibling tool (for example the build-creation tool) as the alternative for starting or restarting work, so it stops short of full when/when-not/alternatives coverage.

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.