Skip to main content
Glama

Outil.io

Get video project

get_video_project
Read-only

Lire le document complet, les ids de ses éléments et la version nécessaire aux prochaines éditions.

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": "get_video_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety profile is covered. The description adds useful output-level context (full document, element ids, edit version), but does not explain whether the version is required for concurrency control, what happens if it is stale, or the response shape — modest added value beyond annotations.

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, and the most decision-relevant detail (the version needed for future edits) is placed at the end of the clause. Minor deduction for the language mismatch with the English title and sibling names, and for the vague "document" wording.

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 simple one-parameter read tool with annotations covering safety and no output schema, the definition is close to adequate. It still leaves the agent guessing what the resource actually is, how projectId should be sourced, and what the returned "document" contains structurally.

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?

There is a single parameter, projectId, with 0% schema description coverage, and the description says nothing about it. The parameter is largely self-explanatory from its name and uuid format, but the description does not compensate for the documentation gap (e.g., where to obtain a projectId).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb is clear ("Lire") and it specifies what is returned: the full document, its element ids, and the version needed for subsequent edits. However, it never names the resource — it says "le document" rather than "video project" — so the agent must rely on the tool name to know what is being read, and it does not distinguish itself from siblings such as get_video_export or list_video_projects.

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?

Usage is implied rather than stated: "la version nécessaire aux prochaines éditions" hints that this should be called before making edits to obtain the current version. There is no explicit when-to-use/when-not, no mention of prerequisites, and no reference to alternatives like list_video_projects.

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.