Skip to main content
Glama

Studio Ghibli

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Vehicles

vehicles
Read-onlyIdempotent

List vehicles from Studio Ghibli films (up to optional limit), returning name, description, vehicle class, length, pilot, and the film it appears in.

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": 8
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Vehicle description",
+            "type": "string"
+          },
+          "films": {
+            "description": "Array of film IDs",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "description": "Vehicle unique identifier",
+            "type": "string"
+          },
+          "length": {
+            "description": "Vehicle length",
+            "type": "string"
+          },
+          "name": {
+            "description": "Vehicle name",
+            "type": "string"
+          },
+          "pilot": {
+            "description": "Pilot ID",
+            "type": "string"
+          },
+          "url": {
+            "description": "API URL for this vehicle",
+            "type": "string"
+          },
+          "vehicle_class": {
+            "description": "Vehicle class/type",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish the tool as read-only, idempotent, and non-destructive. The description adds behavioral context about the optional limit and the fields returned, which is not specified in the annotations or schema. It does not address edge cases like default limits or empty results, but is adequate.

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, well-structured sentence that front-loads the primary purpose and includes the parameter in a concise parenthetical. No extraneous information is present.

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, output schema present, and strong annotations), the description sufficiently covers the tool's purpose, return fields, and parameter semantics. It is complete for an agent to select and invoke this tool appropriately.

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's only parameter, 'limit', lacks a description. The description compensates by explaining the parameter's role as an optional cap on the number of results, which is the key semantic information. It doesn't specify validation rules but is sufficient for a single optional parameter.

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 clearly states the action ('List'), the resource ('vehicles'), and the scope ('from Studio Ghibli films'). It enumerates the returned fields, distinguishing it from the singular 'vehicle' sibling tool by implying a plural listing.

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?

The description implies its use case as a list endpoint and mentions the optional limit, but it does not explicitly contrast with the singular 'vehicle' tool or state when to prefer one over the other. There is no explicit when/when-not guidance.

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