Skip to main content
Glama

Studio Ghibli Locations

studio_ghibli_locations
Read-onlyIdempotent

List fictional locations from Studio Ghibli films (up to optional limit), returning name, climate, terrain, surface water, 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": 15
    },
    "name": "studio_ghibli_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered and the description needn't restate it. What the description adds is the returned attribute set (name, climate, terrain, surface water, films), but it omits pagination/ordering behavior and what happens when limit is omitted, which are the meaningful remaining traits for this tool.

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 sentence, front-loaded with the verb and resource, with no filler or redundant preamble. The parenthetical '(up to optional limit)' is slightly awkwardly placed mid-sentence, but it is not wasted text.

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?

A simple, single-parameter, read-only listing tool with an output schema, so return-value documentation is already handled and the description's field list is a bonus. Remaining gaps (default limit, ordering, whether 'films' is a list) are minor for a tool this simple.

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?

The single parameter 'limit' has 0% schema description coverage, so the description must carry it — and it does only partially, clarifying that the cap is optional and that results are bounded 'up to' it. It does not state the default when omitted or any maximum, leaving the agent to guess on the one parameter that exists.

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 fictional locations from Studio Ghibli films', plus the fields returned. The plural 'locations' contrasts implicitly with the singular sibling studio_ghibli_location, but the description never names or references that alternative, so differentiation is left to inference.

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?

Usage is implied by the verb 'List' and the note that a limit is optional, giving a vague sense that this is a bulk enumeration with an optional cap. There is no explicit when-to-use statement, no exclusion, and no pointer to the singular single-record sibling.

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.