Skip to main content
Glama

Outil.io

Get video guide

get_video_guide
Read-only

Mode d’emploi du studio vidéo : montage multipiste, coordonnées, lots atomiques, inspection visuelle, import et contrôle de livraison. Lire avant une tâche vidéo.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_video_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds that the content is instructional documentation rather than data, which is useful, but says nothing about length, format of the returned guide, or how to consume it. With annotations carrying the safety burden, a 3 is appropriate.

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 clauses with the topic inventory up front and the call-to-action last; no filler and nothing redundant. Well sized for a zero-parameter guide retrieval.

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?

For a parameterless, side-effect-free documentation fetch with no output schema, the definition covers what the guide contains and when to read it. The only real gap is the absence of any hint about the response format or size, which is minor here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so no parameter meaning needs to be conveyed and the baseline of 4 applies. The description correctly implies a parameterless fetch of documentation.

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 the resource precisely — a user manual ('mode d'emploi') for the video studio — and enumerates the domains it covers (multitrack editing, coordinates, atomic batches, inspection, import, delivery checks). It is clearly distinct from action siblings like add_video_clip, though it does not distinguish itself from the other guide tools such as get_template_import_guide despite overlapping on 'import'.

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?

'Lire avant une tâche vidéo' gives an explicit trigger condition for invoking the tool, which is exactly the guidance an agent needs for a documentation tool. It stops short of saying when NOT to read it or which sibling guide to prefer for adjacent topics.

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.