Skip to main content
Glama

GuideDoc Documentary Database

Explore public documentary subjects

browse_topics
Read-only

Find public genre/topic collections and canonical page links.

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

Input Schema

NameRequiredDescriptionDefault
kindNotopic
pageNo
limitNo
queryNo
languageNoen

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 / language / const
      Added value: +"en"
    • removedInput schema / properties / language / enum
      Removed value: -[
      -  "en",
      -  "ca",
      -  "es"
      -]
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  4. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, open-world, non-destructive operation, so the description does not need to repeat that safety profile. It adds only that results are "public" and include "canonical page links," without describing pagination, filtering behavior, or how query matching works.

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 a single front-loaded sentence with no wasted words. However, its extreme brevity leaves important qualifiers and usage constraints unstated.

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 five-parameter browsing tool with no schema parameter descriptions, one sentence is not enough to explain filtering, pagination, and language behavior. The output schema and annotations cover returns and safety, but the description still leaves significant gaps around how to invoke the tool correctly.

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 needs to compensate for five undocumented parameters. It only loosely maps "genre/topic" to the kind enum and says nothing about page, limit, query, or the fixed language parameter.

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 states a clear verb and resource: "Find public genre/topic collections and canonical page links." It is understandable without opening the schema, but it does not differentiate this browsing tool from siblings such as catalogue_search or search_documentaries.

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 explicit guidance on when to use browse_topics instead of search or catalogue_search, nor any stated prerequisites or exclusions. The browsing/discovery use case is only implied by the verb "Find" and the word "collections."

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