Skip to main content
Glama

David's video episodes as text

get_david_episodes
Read-only

Video news episodes of Orb Studio anchor David (TikTok) with a text version: title, date, topic, summary, the anchor's lines in Russian and German, sources, a watch link and data_snapshot (state of the Orb Studio radars on the episode date: risk index and top headline per radar; a daily snapshot, null when none was saved). Use it to summarise an episode for a user, see what data the episode was made from, and link the video.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax episodes (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral detail beyond that: data_snapshot is a per-episode-date daily snapshot with risk index and top headline per radar, and is null when none was saved — important null-handling context. It stops short of stating ordering (newest first?) or what happens when the store is empty.

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 description is front-loaded with what the tool returns and then states its uses, with no filler sentences. The field enumeration is long but each field earns its place; a slight trim (e.g. compressing the Russian/German lines detail) would make it crisper.

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?

With no output schema, the description carries the burden of describing return content, and it does so thoroughly, including nested data_snapshot semantics and its null case. The remaining gap is ordering/pagination behavior for the limit-bounded list, which an agent would need to describe results correctly.

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 description coverage is 100% and the single parameter 'limit' is fully documented there (max 20, min 1, default 5). The description says nothing about the limit parameter or about result ordering, so it adds no meaning beyond the schema. Baseline 3 applies.

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 a specific resource ('Video news episodes of Orb Studio anchor David (TikTok) with a text version') and enumerates the fields returned, so the agent knows exactly what it retrieves. It does not, however, distinguish itself from nearby siblings such as ask_david, get_broadcast, or get_history, which is the only missing element for a 5.

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?

'Use it to summarise an episode for a user, see what data the episode was made from, and link the video' gives concrete use scenarios. There are no exclusions and no explicit routing to alternatives (e.g. ask_david for questions about David), so the guidance is clear but incomplete.

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.