Skip to main content
Glama

Search People

search_people
Read-onlyIdempotent

Searches Korean film personnel such as directors, actors, and staff by name or filmography, returning IDs that can be used to retrieve detailed profile information.

Instructions

영화인(감독, 배우, 스태프)을 검색합니다. 결과의 people_cd 로 get_person_info 를 호출할 수 있습니다.

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
nameNo영화인 이름
pageNo페이지 번호 (1부터)
per_pageNo페이지당 결과 수 (최대 100)
filmographyNo참여 영화명으로 필터

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds a useful post-call chain (people_cd → get_person_info) but says nothing about matching semantics (exact vs partial name), empty-result behavior, or pagination limits beyond what the schema already documents.

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?

Two sentences, purpose first and follow-up flow second, with no redundant restatement of the title or schema. Every sentence carries information an agent needs.

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, return values need no explanation, and rich annotations cover the safety profile. The description is adequate for a simple search tool, though it leaves filter-combination behavior (name + filmography together) unstated.

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 description coverage is 100%: `name`, `page`, `per_page` and `filmography` each carry Korean descriptions with bounds and defaults in the schema itself. The description adds no parameter-level meaning (e.g., how `filmography` matches titles), so the baseline of 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 states a specific verb and resource ('영화인(감독, 배우, 스태프)을 검색합니다') and enumerates the entity subtypes covered, so an agent knows this targets people rather than movies or companies. It does not explicitly contrast with a competing search tool, but no sibling overlaps this resource.

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 concrete workflow guidance: take `people_cd` from the results and pass it to `get_person_info`, which routes the agent correctly in a search-then-detail sequence. There is no guidance on when to prefer `name` vs `filmography` filtering or on when not to use this tool.

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