Skip to main content
Glama

GuideDoc Documentary Database

Explore related documentaries

catalogue_related
Read-only

Recommendations based on public subjects and credits, with reasons.

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": {
      "similar_to_id": "<similar_to_id>"
    },
    "name": "catalogue_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
filtersNo
languageNoen
similar_to_idYes

Output Schema

NameRequiredDescriptionDefault
dataYes
sourceNoGuideDoc public documentary information; catalogue availability is not a playback entitlement

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / source / default
      Previous value: -"GuideDoc public information only; full films require an eligible subscription and territory"New value: +"GuideDoc public documentary information; catalogue availability is not a playback entitlement"
  2. Added

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered; the description adds almost nothing beyond that. "With reasons" hints at an explanation field in the response, but since an output schema exists this is redundant rather than informative, and pagination/ranking behavior is not disclosed.

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

Conciseness2/5

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

It is short and front-loaded, but the brevity is under-specification rather than efficiency — a single sentence that omits the one required argument. Almost no information is delivered for the space it takes.

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

Completeness2/5

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

For a recommendation tool with a required seed id, a large filter object and pagination, the description leaves the agent unable to call it correctly without reading the schema cold. The presence of an output schema excuses explaining return values, but the input side and the sibling routing are entirely missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, including the required similar_to_id and a nested filters object with ten fields, yet the description names none of them. It neither explains the seed id nor what the filters constrain, so it contributes nothing to parameter understanding.

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

Purpose2/5

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

"Recommendations based on public subjects and credits, with reasons" restates the title's idea of related documentaries without saying what the tool actually operates on — it never mentions that it takes a seed film id and returns similar titles. It is indistinguishable in practice from the sibling recommend_documentaries, and no evidence in the sentence explains how the two differ.

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 when-to-use guidance at all: nothing says this requires an existing documentary id, nothing says when to prefer it over recommend_documentaries or catalogue_search. The only hint is the vague phrase "based on public subjects and credits", which does not translate into a selection rule.

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