Skip to main content
Glama

GuideDoc Documentary Database

Read public biography and filmography

get_person
Read-only

Read a published person's biography and only their public documentary records.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
pageNo
limitNo
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.4/5.0
Behavior4/5

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

Read-only, non-destructive, and open-world behavior are already covered by annotations, so the description only needed to add context. It does add meaningful disclosure that results are limited to published people and public documentary records, which explains why some records may be absent. Pagination over the record list is not mentioned, which is the remaining gap.

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?

A single front-loaded sentence with no padding, and the scope restriction is placed where it is read first. It is efficient, though the brevity borders on under-specification given the parameter omissions.

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 values need not be described, and annotations cover the safety profile. That leaves the undocumented pagination parameters as the main incompleteness, which is a real gap for a tool that returns a list of documentary records capped at 20 per page.

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 the burden of explaining the four parameters, and it does not. It never clarifies that 'id' is the required person identifier or what page and limit control, leaving the agent to infer pagination from bare integer fields.

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 specific verb (Read) and a concrete resource (a person's biography plus documentary records), and the word 'published' scopes it to a subset of people. That distinguishes it from search_people and get_documentary, though it never names those siblings explicitly.

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?

Usage is only implied: you use this when you already have a person id and want their bio plus linked documentaries. The phrase 'only their public documentary records' hints at a scope restriction, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool when you lack an id.

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