Skip to main content
Glama

GuideDoc Documentary Database

Explore documentaries

open_catalogue
Read-only

Search and display documentary titles, filmmakers or topics inside GuideDoc.

When this explorer is active, use for bare or ambiguous titles before answering
from another meaning: 'Mon Petit' means query='Mon Petit', not a translation.
Honor explicit translation/unrelated requests. Nonempty queries default to all
documentary records, ranked by relevance; original_title identifies alternate
names. Preserve filters explicitly requested by the user. For no matches, ask
for identifying details; never invent a film. Empty arguments open
all documentary records, newest first. Full films retain normal access requirements.

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": "open_catalogue"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
queryNo
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

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive and open-world, and the description adds genuine behavior on top: non-empty queries default to all records ranked by relevance, empty arguments return all records newest first, and 'Full films retain normal access requirements' flags that results may be gated. Pagination behavior and what a result record contains are left unstated, which keeps it short of a 5.

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 purpose, then behavior, then failure handling, in a compact block with no filler sentences. The phrasing is dense to the point of being run-on in places (the 'when this explorer is active' clause plus the Mon Petit example crammed into one sentence), but every line carries information.

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

Completeness3/5

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

An output schema exists, so return format needn't be spelled out, and the description covers the search and empty-result paths adequately. Gaps remain around the explorer_id lifecycle (who sets it, what a missing value means) and around pagination and sort semantics across the eleven nested filter fields, which matters for a tool with this much surface area.

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 0%, so the description has to carry the parameter burden and it only partly does. It explains query semantics (bare title matching, original_title as an alternate-name field) and warns that user-specified filters must be preserved, which is useful. Page, limit, explorer_id, language and nearly all the nested filter fields (sort, scope, genre, year ranges) get no explanation at all.

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?

States a specific verb-and-resource pair: 'Search and display documentary titles, filmmakers or topics inside GuideDoc.' That is concrete enough to distinguish it from generic fetching. It loses a point because it never names the siblings an agent must choose between (search_documentaries, catalogue_search, search), and the recurring notion of 'this explorer' is never defined for a first-time caller.

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?

Offers real usage rules: use it for bare or ambiguous titles before reinterpreting them ('Mon Petit' means query='Mon Petit'), honor explicit translation requests, and ask for details rather than inventing a film when nothing matches. What it lacks is routing guidance against the many lookalike siblings; without that, an agent still has to guess whether open_catalogue or search_documentaries is the correct entry point.

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