Skip to main content
Glama

Get person

tvmaze_get_person
Read-onlyIdempotent

Search people by name to return candidates, then select a person_id to list their cast, guest, or crew credits. Name searches never select a person automatically. Credits preserve source order and page at 50 rows by default, up to 250 per call; show_id chains to tvmaze_get_show or tvmaze_get_episodes, and guest episode_id chains to tvmaze_get_cast with scope "episode".

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size for person_id only. Defaults to 50; requests above 250 are clamped to 250.
queryNoPerson name to search. Supply query or person_id, never both. Blank is unset.
cursorNoPrevious next_cursor for person_id only; the current limit sets page size.
person_idNoTVmaze person id from tvmaze_get_cast or this tool’s candidates.
credit_kindNoCredit category for person_id only. Defaults to cast.

Output Schema

NameRequiredDescriptionDefault
capNoApplied page size or possible source search ceiling.
kindNoSearch candidates or one selected person with credits.
errorNoPresent when the call failed. Absent on success.
shownNoActual number of candidates or credits returned.
noticeNoCandidate selection, empty result, paging, and clamp guidance.
personNoSelected person profile.
creditsNoSelected credits on this page, in source order.
has_moreNoWhether further credit rows remain.
truncatedNoMore credits remain, or the source may have capped search candidates.
candidatesNoName search candidates, in source order. Never automatically selected.
totalCountNoCandidates returned by search, or total selected credits before paging.
credit_kindNoCredit category returned for the selected person.
next_cursorNoContinuation token for the selected credit list.
effectiveQueryNoTrimmed person name searched.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedOutput schema / properties / credits / items / properties / airdate
      Added value: +{
      +  "description": "TVmaze date label (YYYY-MM-DD): the programming day or announced release date. Preserve it as a label without combining it with a clock time.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / credits / items / properties / episode_number
      Added value: +{
      +  "description": "Number within the season on a guest episode credit.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / credits / items / properties / season
      Added value: +{
      +  "description": "Season number on a guest episode credit.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / credits / items / properties / show_ended
      Added value: +{
      +  "description": "Last air date of the show on cast and crew credits.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / credits / items / properties / show_premiered
      Added value: +{
      +  "description": "First air date of the show on cast and crew credits.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / credits / items / properties / show_status
      Added value: +{
      +  "description": "Production status of the show on cast and crew credits.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and open-world, so safety is covered; the description adds value with credit ordering ('preserve source order') and the default/ceiling paging behavior. It does not discuss empty-result handling or error cases, which keeps it short of a 5.

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?

Three sentences, front-loaded with the search-then-select pattern before paging and chaining details. It is dense—several concepts per sentence—but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values needn't be described, and the definition still covers the mode split, paging limits, ordering, and cross-tool chaining. For a read-only lookup tool with five optional parameters, nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond by explaining that limit/cursor/credit_kind apply only to the person_id mode and that query and person_id are alternatives. It also notes where a valid person_id comes from (tvmaze_get_cast or this tool's candidates), adding real selection guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names two concrete modes—name search returning candidates, and person_id lookups returning cast/guest/crew credits—so the verb and resource are unambiguous. It also separates itself from siblings by naming tvmaze_get_cast, tvmaze_get_show, and tvmaze_get_episodes as the downstream tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It explicitly states the workflow (search, then pick a person_id) and warns that name searches never auto-select a person, removing the main ambiguity between the two modes. It also names the specific tools to chain to for show and guest-episode follow-ups, which is exactly the routing an agent needs.

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.