Skip to main content
Glama

Get person profile

get_person
Read-onlyIdempotent

Person affiliations, identifiers, project and section roles, credited items, publications, podcasts, videos, Cluster Chronicles works and collaborators. Lists cap at 50 with totals. Use id to disambiguate.

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

Input Schema

NameRequiredDescriptionDefault
idNoExact person Omeka id or typed id (person:123); required to disambiguate homonyms
nameNoFull name in either order, with or without accents: 'Beier, Ulli' and 'Ulli Beier' both resolve

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
    • changedInput schema / properties / id / anyOf
      Previous value: -[
      -  {
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "maxLength": 64,
      -    "type": "string"
      -  }
      -]New value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "maxLength": 64,
      +    "type": "string"
      +  }
      +]
  3. Changed4 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "exclusiveMinimum": 0,
      +      "maximum": 9007199254740991,
      +      "type": "integer"
      +    },
      +    {
      +      "maxLength": 64,
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Exact person Omeka id or typed id (person:123); required to disambiguate homonyms"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Either name order, with or without accents: 'Beier, Ulli' and 'Ulli Beier' both resolve"New value: +"Full name in either order, with or without accents: 'Beier, Ulli' and 'Ulli Beier' both resolve"
    • addedInput schema / properties / name / maxLength
      Added value: +1000
    • removedInput schema / required
      Removed value: -[
      -  "name"
      -]
  4. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description contributes a genuinely non-obvious behavioral fact: embedded lists are capped at 50 with totals reported. That tells the agent results may be truncated without being incomplete-looking. It still omits what happens when a name matches several people, but the added context is real value beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no padding, but the first sentence is an unstructured comma list of nouns rather than a statement of what the tool does, so the reader must assemble the purpose themselves. The cap/totals caveat and the id hint are tacked on as fragments rather than prioritized.

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?

With no output schema, the description must carry the return shape and does partially: it names the categories of data returned and the 50-item list cap. It does not explain whether both id and name may be supplied, what a name-only lookup returns on multiple matches, or how the profile relates to the pointers toward other entities (e.g., whether they are inline or require follow-up tools).

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%, so both parameters are already documented with format and homonym-disambiguation notes. "Use id to disambiguate" restates what the id field description already says and adds no new syntax or precedence rules; baseline 3 applies.

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

Purpose3/5

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

The description enumerates the resource contents (affiliations, identifiers, roles, credited items, publications, podcasts, videos, Cluster Chronicles works, collaborators), which makes the subject matter distinguishable from siblings like get_institution or get_project. However, it is a bare noun phrase with no verb and never says it returns a single person's profile keyed by id or name, so the actual operation must be inferred from the tool name and title.

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?

"Use id to disambiguate" gives one conditional directive, but it is about parameter choice rather than tool selection. Nothing states when to use get_person versus search, resolve_entity, get_entity_graph, or find_related for the same subject, so usage is only implied.

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.