Skip to main content
Glama

Get Person Info

get_person_info
Read-onlyIdempotent

Fetch detailed Korean film personnel records by people_cd, including gender, primary field, and filmography, for cast and crew research.

Instructions

영화인 상세 정보(성별, 대표 분야, 필모그래피 등)를 조회합니다.

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": {
      "people_cd": "<people_cd>"
    },
    "name": "get_person_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
people_cdYes영화인 코드 (search_people 결과의 people_cd)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish this as a safe, idempotent, read-only lookup, so the description does not need to repeat that. It adds some value by naming the returned fields, but says nothing about the open-world nature of the lookup, missing-code behavior, or coverage limits for filmography.

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?

One front-loaded sentence with zero filler, and the returned-field list is a useful parenthetical rather than padding. It is efficient, though the extreme brevity means it contributes nothing beyond the structured 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?

With an output schema present, the description need not describe return values, and annotations plus full schema coverage cover safety and the single parameter. The definition is complete for a simple read-only getter, with the only real gap being routing guidance versus the search siblings.

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

Parameters3/5

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

Schema coverage is 100% for the single people_cd parameter, and the schema already states where the value comes from (search_people 결과). The description adds no additional meaning about format, valid ranges, or what happens with an unknown code, so baseline 3 applies.

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 names a specific verb (조회) and resource (영화인 상세 정보) and even enumerates what detail is returned (성별, 대표 분야, 필모그래피). It is clearly distinguishable from sibling search tools, but it never names search_people as the prerequisite even though the schema does, so differentiation is only implicit.

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: an agent can infer this is the follow-up call after obtaining a people_cd. There is no explicit when-to-use, no when-not-to-use, and no mention of the sibling it pairs with, so guidance is left to inference.

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