Skip to main content
Glama

GuideDoc Documentary Database

Open explorer film details

catalogue_film
Read-only

Revalidate publication before displaying public editorial film details.

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": {
      "id": "<id>"
    },
    "name": "catalogue_film"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
filtersNo
languageNoen
explorer_idNo

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

C2.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a precondition ('Revalidate publication before displaying'), which is useful context beyond annotations, but it does not explain what revalidation means, what happens on failure, or what access requirements exist.

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 description is a single sentence with no wasted words, but it is front-loaded with an ambiguous revalidation instruction rather than the tool's primary action. It is concise yet under-specified for a tool with a nested filters object.

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?

Although an output schema exists and annotations cover the read-only safety profile, the description does not explain the required id, the many optional filters, the language constraint, or the explorer_id. For a film-detail lookup with nested filtering, this is not complete enough to guide correct invocation.

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% and the description does not explain any of the four parameters. It says nothing about the required film id, the optional filters object, the language field, or the explorer_id, leaving the agent with no semantic guidance beyond the raw schema.

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 suggests retrieving and displaying editorial film details, but the verb is vague and wrapped in jargon ('Revalidate publication'). It does not distinguish this tool from siblings such as get_documentary, catalogue_search, or catalogue_related.

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, no alternatives named, and no prerequisites or exclusions beyond the vague 'revalidate publication' phrase. An agent cannot tell from the description when this tool is the correct choice.

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