Skip to main content
Glama

GuideDoc Documentary Database

Search and filter documentaries

search_documentaries
Read-only

Search and display documentary films in the GuideDoc explorer. Use concise title, director or topic terms and explicit filters. Keep the latest query and filters for follow-ups, changing only what the user requests. Unrestricted searches cover all records. English metadata; audio/subtitle filters remain independent. Pass explorer_id from the active explorer context to update its view.

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

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. Changed2 schema fields changed
    • addedInput schema / properties / explorer_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "pattern": "^[0-9a-f]{32}$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Explorer Id"
      +}
    • changedInput schema / title
      Previous value: -"search_documentariesArguments"New value: +"visual_search_documentariesArguments"
  3. Changed2 schema fields changed
    • addedInput schema / properties / language / const
      Added value: +"en"
    • removedInput schema / properties / language / enum
      Removed value: -[
      -  "en",
      -  "ca",
      -  "es"
      -]
  4. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  5. Added

TDQS

B3.3/5.0
Behavior4/5

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

With annotations already marking it read-only, open-world, and non-destructive, the description adds relevant behavior: English metadata, independent audio/subtitle filters, unrestricted searches covering all records, and explorer_id updating an active explorer view. It does not disclose pagination behavior, but it contributes meaningful context beyond the annotations.

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 purpose is front-loaded and the description stays compact across five sentences with little obvious filler. Some phrases such as "Unrestricted searches cover all records" are somewhat vague, but overall the structure is efficient.

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?

The tool has six top-level parameters plus a nested filter object with many subfields, yet the description gives only partial filter semantics and no explanation of pagination or sort/scope behavior. The output schema reduces the need to describe return values, but the description remains thin for a search tool of this complexity.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, but it only clarifies query terms and a few filter concepts like director, topic, and audio/subtitle independence. It leaves sort, scope, genre, country, year_from/year_to, festival, max_duration_minutes, page, limit, and language unexplained beyond their field names.

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 gives a clear verb and resource: "Search and display documentary films in the GuideDoc explorer." It does not explain how this differs from siblings such as search, catalogue_search, or recommend_documentaries, so it falls short of 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful invocation guidance such as using concise title, director or topic terms, explicit filters, and preserving prior query state for follow-ups. However, it never states when to choose this tool over catalogue_search, search, or recommend_documentaries, so the guidance is implied rather than comparative.

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