Skip to main content
Glama

Studio Ghibli

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Species

species
Read-onlyIdempotent

List species that appear in Studio Ghibli films (up to optional limit), returning name, classification, eye/hair colors, and the films and characters associated with that species.

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "classification": {
+            "description": "Species classification",
+            "type": "string"
+          },
+          "eye_colors": {
+            "description": "Eye colors for species",
+            "type": "string"
+          },
+          "films": {
+            "description": "Array of film IDs",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "hair_colors": {
+            "description": "Hair colors for species",
+            "type": "string"
+          },
+          "id": {
+            "description": "Species unique identifier",
+            "type": "string"
+          },
+          "name": {
+            "description": "Species name",
+            "type": "string"
+          },
+          "people": {
+            "description": "Array of person IDs",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {
+            "description": "API URL for this species",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the tool safe (readOnly, idempotent, non-destructive), and the description adds useful details about the optional limit and the specific fields returned. These are behavioral insights beyond the annotations, and there is no contradiction.

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

Conciseness5/5

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

The description is a single, efficiently structured sentence that begins with the verb and resource. It contains no filler or redundant repetition of the title or schema.

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

Completeness5/5

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

Given the tool's simplicity (one optional parameter, no required parameters), existing output schema, and rich annotations, the description covers all essential aspects: purpose, scope, optional limit, and return content. No critical information is missing.

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

Parameters4/5

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

The schema has only one parameter with 0% description coverage, but the description clarifies that 'limit' is optional and caps the number of results ('up to optional limit'). This adds meaning beyond the bare parameter name and partially compensates for the missing schema description.

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

Purpose5/5

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

The description uses the specific verb 'List' with the resource 'species that appear in Studio Ghibli films' and enumerates the returned fields, clearly establishing the tool's purpose. It distinguishes itself from the sibling tool 'species_one' by implying a list operation rather than a single-entity lookup.

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

Usage Guidelines4/5

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

The phrase 'List species...' provides clear context for when to use this tool, and 'up to optional limit' further defines the usage shape. It does not explicitly name alternatives or exclusions, but the intended use case is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Studio Ghibli toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources