Skip to main content
Glama

Studio Ghibli Location

studio_ghibli_location
Read-onlyIdempotent

Single location 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": "6e173f76-584d-4255-bb08-b42b8d1d91d0"
    },
    "name": "studio_ghibli_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
idNoLocation unique identifier
urlNoAPI URL for this location
nameNoLocation name
filmsNoArray of film IDs
climateNoClimate description
terrainNoTerrain description
residentsNoArray of resident IDs
surface_waterNoSurface water percentage

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds nothing beyond that — no note on what happens with an unknown id, no auth or rate-limit context, no indication of lookup-vs-external-fetch behavior implied by openWorldHint.

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?

Five words with zero redundancy and the key qualifier ('single', 'by id') front-loaded, but the brevity is under-specification rather than economy — there is no second sentence carrying the information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be described. However, for a single-record lookup with a 0%-documented required id and an openWorldHint suggesting external data, the definition leaves the agent without the domain meaning of 'location' or any indication of error behavior.

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%, so the description must compensate for the single undocumented 'id' parameter. 'by id' only restates that the id selects a location; it gives no format, provenance (where to get a valid id), or example, even though the schema's example field is the only hint of the UUID form.

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 phrase 'Single location by id' identifies the resource ('location') and its scope (single, keyed by id), which does separate it from the plural sibling studio_ghibli_locations. But it omits a real verb (fetch/retrieve/describe) and never says what a 'location' actually is in this domain, leaving the purpose only implied.

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 when-to-use guidance, no mention of the list sibling as an alternative, and no stated precondition such as needing an id obtained from studio_ghibli_locations. The singular/plural contrast is the only implicit routing signal.

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.