Skip to main content
Glama

Studio Ghibli Person

studio_ghibli_person
Read-onlyIdempotent

Single person by id.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "ba510c6d-61ae-45a6-8b5a-3dd06b4bed34"
    },
    "name": "studio_ghibli_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
idNoPerson unique identifier
ageNoCharacter age
urlNoAPI URL for this person
nameNoCharacter/person name
filmsNoArray of film IDs
genderNoCharacter gender
speciesNoSpecies ID
eye_colorNoEye color
hair_colorNoHair color

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered without description help. The description adds nothing beyond that — no note on what a lookup miss returns, whether the id format is a UUID (only visible in the schema example), or what data class 'person' covers. With annotations doing the heavy lifting, this is a minimal-value description rather than a contradiction.

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?

Four words with zero padding and the key qualifier ('by id') is front-loaded, so there is no wasted text. But brevity here crosses into under-specification — the fragment omits even a verb, so it is concise without being informative.

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?

The tool is simple (one required string), annotations cover safety and idempotency, and an output schema exists so return values need no explanation. What remains missing is the linkage to the sibling list tool for obtaining valid ids and the behavior on an unknown id, which matters even for a trivial getter.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description must carry the meaning. 'by id' merely restates the parameter name; the only signal about the id's shape is a UUID example inside the schema, not the description. No indication of whether the id is the same one returned by studio_ghibli_people.

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?

"Single person by id" identifies the resource (a person) and the lookup key (id), and the singular 'person' implicitly contrasts with the plural sibling studio_ghibli_people. However, it is a sentence fragment with no verb and never explicitly distinguishes itself from the list tool, so the agent must infer the retrieve-one semantics from the name alone.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus studio_ghibli_people, which is the obvious alternative for the same resource. No prerequisites, no note on what happens when an unknown id is supplied, and no indication of whether ids come from the people listing.

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.