Skip to main content
Glama

Fact-check a YouTube interview (crypto forecasts)

check_interview

Send a YouTube link. Orb Studio reads the captions, lists checkable claims with timecodes (price targets with deadlines, forecasts, facts, the speaker's own interest, pressure on the listener) and checks crypto price targets whose deadline has passed against Kraken daily prices: reached / not reached / too early / no data. Already checked videos are free; new videos are limited per day. AI paraphrase — approximate; a missed target is not proof of lying.

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": {
      "url": "<url>"
    },
    "name": "check_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds the material behavior on top of that: a daily quota for new videos, free reprocessing of cached ones, the full verdict vocabulary (reached / not reached / too early / no data), Kraken daily prices as the data source, and an explicit accuracy caveat about AI paraphrase. That is exactly the kind of cost, sourcing and reliability context annotations cannot carry.

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?

Front-loaded with the action and input in the first sentence, then layered output description, pricing/quota, and disclaimer in a logical order. The parenthetical claim taxonomy is dense but each clause carries real information; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, the description fully covers what comes back (claims with timecodes, verdict categories), the pricing model, and the interpretation caveat. An agent has everything needed to call it and to set expectations about the result.

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 required parameter with 100% schema description coverage, so the schema already fully documents what to supply. The description repeats 'YouTube link' without adding constraints such as whether shorts, live URLs, or non-English captions are accepted, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource (fact-check a YouTube interview) and then enumerates exactly what is produced: checkable claims with timecodes and price-target verdicts. An agent can distinguish this from a retrieval tool like get_interview_checks without opening the schema.

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?

'Send a YouTube link' makes the required input clear, and the note that already-checked videos are free vs. new videos being daily-limited implies when a run is cheap. However, it never says when to call this rather than the sibling get_interview_checks for already-analyzed videos, so the routing decision is left to inference.

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.