Skip to main content
Glama

Record how a video turned out

rate_video

When log_video asks you to: the member's 1 to 5 answer to "How did this video turn out?", with their words. A low score reaches the Cuttr team, who help them the same day.

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": {
      "video_id": "<video_id>",
      "score": "<score>"
    },
    "name": "rate_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
scoreYes
commentNoWhat they said about it, in their words
video_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does add one important fact: a low score escalates to the Cuttr team, who respond the same day. That is genuinely valuable consequence disclosure. It omits, however, whether a rating can be revised or overwritten, what threshold counts as low, and what the tool returns, which matters for a write operation with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, and the escalation note is worth its space. The structure is poor though: the leading 'When log_video asks you to:' is a sentence fragment that the rest of the clause never grammatically completes, forcing the reader to reconstruct the meaning.

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 three-parameter write tool with no annotations and no output schema, the definition covers the trigger and the downstream consequence, which are the two hardest things to infer. It still leaves the escalation threshold, the update-versus-create semantics, and the meaning of video_id undocumented.

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 coverage is 33%, with only comment documented inline. The description partially compensates by glossing score as the member's 1-5 answer and comment as their words, which reinforces the schema's minimum/maximum rather than adding new syntax. video_id remains entirely unexplained and must be inferred as the video being rated.

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 (a video) and the action (recording the member's 1-5 answer plus their own words), and ties it to the log_video flow so an agent can distinguish it from the sibling that triggers it. The phrasing is fragmented — it opens with a dangling clause rather than a verb — but the intent is recoverable.

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?

It gives a clear invocation condition: call this when log_video asks you to. That is a real, actionable trigger rather than a vague 'use when appropriate'. It stops short of naming when not to call it or what to do if the member declines, so it is not a full 5.

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