Skip to main content
Glama

kelpo_video_download

Read-onlyIdempotent

Get a private video download link, valid for 15 minutes and revoked with this access key. Arguments: {"path": {"id": ""}}

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": {
      "path": "<path>"
    },
    "name": "kelpo_video_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower; the description nonetheless adds real context: the link is private, expires in 15 minutes, and is revoked with the access key. It does not describe what happens when the link is expired or whether repeated calls produce new links (relevant given idempotentHint).

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?

The behavioral statement is front-loaded and tight. The trailing arguments echo is mildly redundant with the input schema, but it does not bloat the definition.

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?

Key behavioral facts (validity window, revocation) are present and there is no output schema to explain, but the nested parameter's meaning is left unaddressed, which is the main gap for an agent trying to invoke this correctly.

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 parameter is a nested object with an undocumented 'id' field. The description merely restates the schema shape ('{"path": {"id": "<id>"}}') without explaining whether the id is a video id, take id, or project id — the exact ambiguity the agent needs resolved.

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 verb and resource — obtaining a private video download link — and adds its lifetime (15 minutes) and revocation condition. It is clearly distinct from siblings like kelpo_videos or kelpo_view_take, though it never names those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to call this versus kelpo_videos (listing videos) or kelpo_view_take (viewing a take), nor any stated prerequisite about the access key. Usage must be inferred entirely from the tool name.

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