Skip to main content
Glama

GuideDoc Documentary Database

Search public filmmakers

search_people
Read-only

Find published filmmaker/contributor profiles linked to public documentaries.

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_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. Beyond that, the description adds a genuinely useful behavioral constraint the schema does not encode: only published profiles are returned, and only those linked to public documentaries, so an agent knows unpublished people are silently excluded. It stops short of describing result ordering or how paging behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the entity, the qualifier 'published', and the linkage constraint, with no filler. Nothing in it is redundant against the name or title.

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?

The output schema and annotations relieve the description of explaining returns and safety, but with four undocumented parameters at 0% coverage the description is thin for a paginated search endpoint. An agent still has to infer query matching behavior and pagination semantics from the schema alone, which supplies only bounds and defaults.

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% for all four parameters, so the description carries the full burden of explaining query, language, page, and limit. It says nothing about any of them, not even that 'query' matches names or that 'language' is pinned to English. Only the words 'filmmaker/contributor' vaguely hint at what the free-text query searches.

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: 'Find published filmmaker/contributor profiles', with the scope narrowed to profiles 'linked to public documentaries'. An agent can distinguish it from search_documentaries or search_articles by the returned entity type, but the description never names the closest sibling, get_person, which also returns people.

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 or when-not-to-use guidance: nothing says when to call this versus get_person for a direct lookup or versus the generic search tool. The only implicit signal is the 'published'/'public' scope, which hints the tool will not surface private or unpublished contributors, but no alternative is named.

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