Skip to main content
Glama

Studio Ghibli People

studio_ghibli_people
Read-onlyIdempotent

List Studio Ghibli characters (up to optional limit), returning name, gender, age, eye/hair color, species, and the films they appear in.

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": {
      "limit": 20
    },
    "name": "studio_ghibli_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 fully covered. Beyond that the description adds only that results are capped 'up to optional limit'; it says nothing about default page size, ordering, or truncation behavior, and the return fields it lists are already in the output schema.

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 no filler, and the optional-limit modifier is placed where it matters. The enumeration of return fields is somewhat wasted space given a full output schema exists.

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?

Because an output schema exists, the field list is not needed, and the annotations cover safety, so the remaining obligations are light. However, for a tool that sits beside a single-character sibling, the absence of any routing guidance or default limit leaves it only minimally complete.

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 0% and the single 'limit' parameter has no description, so the description has to compensate. Saying 'up to optional limit' tells the agent the parameter is optional and caps result count, but gives no default value or maximum, leaving the key semantic gap.

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?

States a specific verb and resource ('List Studio Ghibli characters') and enumerates the fields returned, so the agent knows exactly what it retrieves. It does not distinguish itself from the singular sibling studio_ghibli_person or the films/species siblings, so the differentiation is only implied by the verb 'List'.

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?

The description gives no when-to-use guidance, no exclusions, and never mentions the detail-level sibling (studio_ghibli_person) that would be the natural alternative for a single character. The only hint of usage is that a limit can cap results, which is not a selection guideline.

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.