Skip to main content
Glama

Emotional timecodes — human-marked reaction moments in videos

get_clips
Read-only

Moments in interviews where an idea lands on the listener (surprise, delight), marked by a human by eye, plus the rules for finding them from a transcript (listener, pause after a strong line, setup question, stakes). The exact answer is hidden until you predict — honest mode. Each clip has a video link with the start time; fetch the transcript yourself. Use it to train your sense of human reactions.

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_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoClip id, e.g. ER-001
revealNoShow the human-verified answer (default false — predict first)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare read-only and closed-world behavior. The description adds meaningful context beyond that: answers are hidden until reveal, each clip includes a video link with a start time, and the transcript must be fetched separately. It does not cover rate limits or listing behavior, but the added behavioral detail is substantial.

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?

The opening sentence is long and parenthetical, and the clause about "rules for finding them from a transcript" is conceptual padding for a clip-retrieval tool. The operational points—hidden answer, video link, fetch transcript—are present but not front-loaded.

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 two-optional-parameter, read-only tool with no output schema, the description covers the unusual reveal mechanic and the contents of a clip. Its main gap is not clarifying whether an omitted id lists all clips or returns one clip, which matters for correct invocation.

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 100%, so both id and reveal are already documented. The description reinforces the honest-mode meaning of reveal but adds no format or default details beyond the schema, and still leaves unclear whether omitting id returns a single clip or a list.

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 description conveys the flavor of the resource—human-marked emotional moments in interviews—but never states the operation, such as "Retrieve clip metadata" or "List clips." An agent has to infer from the tool name get_clips that it fetches clip records; the text reads more like a training exercise than a retrieval contract.

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?

It implies a predict-then-reveal workflow ("The exact answer is hidden until you predict", reveal defaults to false) and suggests using it to "train your sense of human reactions." However, it never states when to call this versus a sibling like predict, nor does it give explicit alternatives or exclusions.

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.