Skip to main content
Glama

GuideDoc Documentary Database

Refresh explorer results

catalogue_search
Read-only

Search from the explorer without remounting its interface.

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

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

C2.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint true). The description adds one genuine behavioral trait not in the annotations — that the search executes within the existing explorer context and preserves its mounted state, implying the explorer_id carries session state. That is useful but cryptic; it never explains what that stateful context means or how it affects results.

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?

One short, front-loaded sentence with no padding, so there is nothing to trim — but the single sentence spends its space on a UI implementation detail rather than the information an agent needs, making it concise at the cost of usefulness.

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 six-parameter search tool with a nested filter object and pagination, the description is far too thin: it does not identify the searched corpus, the role of explorer_id, or that filtering is supported. The existing output schema excuses it from explaining return values, but the input-side and routing gaps remain substantial.

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 six top-level parameters and a nested 12-field FilmFilters object, so the description carries the full explanatory burden and adds nothing: no mention of query, page/limit bounds, the filters object, or the 32-hex explorer_id format. The word "explorer" is the closest thing to a parameter hint, which is far short of compensating for the coverage gap.

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?

"Search from the explorer without remounting its interface" states a verb but leaves the resource entirely unstated — nothing says it searches films in the catalogue, despite 12 film-specific filter fields in the schema. The only differentiating information is a UI-implementation detail (no remount), and the title "Refresh explorer results" describes a refresh rather than a filtered search, which muddies rather than clarifies.

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?

The phrase "without remounting its interface" implies this is for continuing a search inside an already-open explorer session, which is a faint usage signal, but it never states when to pick this over siblings like search, search_documentaries, browse_topics, or open_catalogue, nor does it say whether an explorer must already exist.

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