Skip to main content
Glama

Outil.io

Validate video project

validate_video_project
Read-only

Vérifier le schéma, l’accès aux médias, les bornes source et les limites avant un export. Ne remplace pas le contrôle visuel/auditif du fichier final.

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": {
      "projectId": "<projectId>"
    },
    "name": "validate_video_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the agent knows this is a safe local check. The description adds useful scope (which dimensions are validated and that a clean result is not a guarantee), but says nothing about whether validation is blocking, how long it takes, or what a failure outcome looks like.

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 short sentences, zero padding, with the primary action stated first and the caveat second. Every clause carries information.

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

Completeness3/5

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

For a validation tool with no output schema, the most important missing piece is the return shape — whether it yields a boolean, a list of issues, or per-check status. The description establishes scope and a caveat but leaves that gap, which matters given the tool's whole purpose is producing a verdict.

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 required parameter (projectId, uuid) is never referenced in the description. The meaning of projectId is inferable from the tool name, but the description adds no semantics beyond the raw schema, leaving the coverage gap uncompensated.

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 names a specific verification action and enumerates what it checks (schema, media access, source bounds, limits) in the context of an export. It's clear what the tool does, though it never explicitly distinguishes itself from adjacent read tools like get_video_project or inspect_video_timeline.

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?

'avant un export' pins down the trigger point for using it, and the second sentence carves out a limitation: it does not substitute for visual/auditory review of the final file. There is no mention of alternatives for cases where validation fails or where a deeper inspection is needed, so it falls short of full when/when-not routing.

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.