Skip to main content
Glama

Search people

search_persons
Read-onlyIdempotent

Find canonical person authority records. Names accept either order and ignore accents. Use resolve_entity to disambiguate homonyms.

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_persons"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 25, max 100
offsetNo
keywordNoMatches the name, a name variant or an affiliation
affiliationNoMatches the person's affiliations only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  3. Changed3 schema fields changed
    • addedInput schema / properties / affiliation / maxLength
      Added value: +1000
    • changedInput schema / properties / keyword / description
      Previous value: -"Matches the name or an affiliation"New value: +"Matches the name, a name variant or an affiliation"
    • addedInput schema / properties / keyword / maxLength
      Added value: +1000
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is fully covered. The description earns some credit for disclosing matching normalization (either name order, accents ignored), which is behavior the schema does not state. It says nothing about result ordering, ranking, or pagination behavior despite neither an output schema nor a described offset parameter.

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?

Three short sentences with the resource statement front-loaded, followed by matching behavior and then the alternative route. Every sentence carries distinct information and there is no restatement of the name or title.

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?

For a four-parameter search tool with no output schema, the definition covers what is searched and how names are matched but not how results are ordered, how large result sets behave, or what offset does. Adequate to invoke, but not enough for an agent to predict result shape or paginate confidently.

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 75%, so the keyword and affiliation parameters are already documented, and the description's accent/order note only marginally extends the keyword semantics. The offset parameter has no schema description and no compensating explanation of pagination anywhere in the definition.

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?

"Find canonical person authority records" gives a specific verb plus a precise resource domain, so an agent knows this is a person lookup over a normalized authority index. It does not distinguish itself from get_person or the generic search tool, so it falls short of the full sibling-differentiation bar.

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?

The final sentence names a concrete alternative (resolve_entity) with the exact condition that selects it (homonym disambiguation), which is real routing guidance. It gives no guidance on when to search here versus fetching a known person by ID via get_person, and no query-shaping advice beyond the ordering/accent note.

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.