Swapi

Get Starship

get_starship

Read-onlyIdempotent

Get a Star Wars starship by its numeric ID. Returns name, model, manufacturer, crew capacity, and hyperdrive rating.

Input Schema

Name	Required	Description	Default
`id`	Yes	Starship ID (e.g., 9 for the Death Star)

Output Schema

Name	Required	Description
`url`	Yes	Starship URL
`MGLT`	Yes	Megalights per hour
`crew`	Yes	Crew capacity
`name`	Yes	Starship name
`model`	Yes	Model
`length`	Yes	Length
`passengers`	Yes	Passenger capacity
`manufacturer`	Yes	Manufacturer
`cargo_capacity`	Yes	Cargo capacity
`starship_class`	Yes	Starship class
`cost_in_credits`	Yes	Cost in credits
`hyperdrive_rating`	Yes	Hyperdrive rating
`max_atmosphering_speed`	Yes	Max atmosphering speed

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "MGLT": {
+      "description": "Megalights per hour",
+      "type": "string"
+    },
+    "cargo_capacity": {
+      "description": "Cargo capacity",
+      "type": "string"
+    },
+    "cost_in_credits": {
+      "description": "Cost in credits",
+      "type": "string"
+    },
+    "crew": {
+      "description": "Crew capacity",
+      "type": "string"
+    },
+    "hyperdrive_rating": {
+      "description": "Hyperdrive rating",
+      "type": "string"
+    },
+    "length": {
+      "description": "Length",
+      "type": "string"
+    },
+    "manufacturer": {
+      "description": "Manufacturer",
+      "type": "string"
+    },
+    "max_atmosphering_speed": {
+      "description": "Max atmosphering speed",
+      "type": "string"
+    },
+    "model": {
+      "description": "Model",
+      "type": "string"
+    },
+    "name": {
+      "description": "Starship name",
+      "type": "string"
+    },
+    "passengers": {
+      "description": "Passenger capacity",
+      "type": "string"
+    },
+    "starship_class": {
+      "description": "Starship class",
+      "type": "string"
+    },
+    "url": {
+      "description": "Starship URL",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "model",
+    "manufacturer",
+    "cost_in_credits",
+    "length",
+    "max_atmosphering_speed",
+    "crew",
+    "passengers",
+    "cargo_capacity",
+    "starship_class",
+    "hyperdrive_rating",
+    "MGLT",
+    "url"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": 9
+  },
+  {
+    "id": 12
+  }
+]

First observedApr 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The annotations already declare the tool as read-only, idempotent, and non-destructive, so the description doesn't need to repeat that. It adds the list of returned fields, but with an output schema known to exist, this is not a significant behavioral disclosure. No additional traits like error handling or data sourcing are mentioned.

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 two short sentences with no redundancy. The first sentence states the core purpose, and the second concisely notes the returned fields, making it appropriately sized and easy to scan.

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 parameter, rich annotations, and an output schema), the description covers everything needed for basic selection. It explains what resource is accessed and what data is returned, with no missing critical context for a read-only lookup.

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 schema already fully documents the 'id' parameter, including type (number) and an example (9 for Death Star). The description's 'numeric ID' adds no new meaning beyond the schema, so it meets the baseline for high schema coverage.

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 a specific verb ('Get') and resource ('Star Wars starship') and clarifies the lookup key ('numeric ID'). It clearly distinguishes itself from sibling get_film and get_planet tools, which target different resources.

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 usage when you have a numeric starship ID, but it does not explicitly state when to use this tool over alternatives like get_film or get_planet. No exclusions or alternative tool references are provided.

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

All Swapi tools Inspect

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.