Skip to main content
Glama

tabii_get_person

Retrieve a tabii cast or crew member by numeric person ID to get their name, job title, and filmography in the chosen language, including show titles, type, year, and genres.

Instructions

One cast/crew member by numeric tabii person id (from a show's cast/directors/writers lists, e.g. Ahmet Kural is 6774). language: "tr" (default), "en", "es", "ar" or "ur". Returns name, job title and their filmography on tabii (title, original title, type, year, genres per show).

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": {
      "person_id": "<person_id>"
    },
    "name": "tabii_get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNotr
person_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does convey that this is a simple id lookup returning profile plus filmography data. It says nothing about invalid-id behavior, whether filmography is paged or truncated, or how language selection falls back when a translation is missing.

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 lookup purpose is front-loaded in the first line and no sentence is filler. The nested parentheticals make the second half slightly dense to parse, but the density buys real information (id provenance, language set, return fields).

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

Completeness4/5

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

For a two-parameter read tool this covers purpose, id provenance, language options and return shape; the presence of an output schema removes the need for the return-field sentence. A short note on behavior for unknown or malformed ids would close the last gap.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description fully compensates: person_id is described as numeric with documented provenance and a worked example, and language is given both its default ("tr") and the accepted set ("en", "es", "ar", "ur") that the schema itself does not enumerate.

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?

States a specific verb and resource ("One cast/crew member by numeric tabii person id") and bounds the unit of return to a single person. The parenthetical clarifies where such an id originates (a show's cast/directors/writers lists), which cleanly separates it from tabii_get_show and tabii_search_content.

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

Usage Guidelines4/5

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

It gives real usage context by telling the agent the person_id must come from a show's cast/directors/writers lists and even supplies a concrete example (Ahmet Kural is 6774). It stops short of naming an alternative tool or a when-not-to-use condition, so it is clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.