Skip to main content
Glama

swapi

by io.github.pipeworx-io

Get Planet

get_planet
Read-onlyIdempotent

Get a Star Wars planet by its numeric ID. Returns name, climate, terrain, population, and orbital data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPlanet ID (e.g., 1 for Tatooine)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPlanet URL
nameYesPlanet name
climateYesClimate
gravityYesGravity
terrainYesTerrain
diameterYesDiameter
populationYesPopulation
surface_waterYesSurface water percentage
orbital_periodYesOrbital period
rotation_periodYesRotation period

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "climate": {
+      "description": "Climate",
+      "type": "string"
+    },
+    "diameter": {
+      "description": "Diameter",
+      "type": "string"
+    },
+    "gravity": {
+      "description": "Gravity",
+      "type": "string"
+    },
+    "name": {
+      "description": "Planet name",
+      "type": "string"
+    },
+    "orbital_period": {
+      "description": "Orbital period",
+      "type": "string"
+    },
+    "population": {
+      "description": "Population",
+      "type": "string"
+    },
+    "rotation_period": {
+      "description": "Rotation period",
+      "type": "string"
+    },
+    "surface_water": {
+      "description": "Surface water percentage",
+      "type": "string"
+    },
+    "terrain": {
+      "description": "Terrain",
+      "type": "string"
+    },
+    "url": {
+      "description": "Planet URL",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "rotation_period",
+    "orbital_period",
+    "diameter",
+    "climate",
+    "gravity",
+    "terrain",
+    "surface_water",
+    "population",
+    "url"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 1
+  },
+  {
+    "id": 8
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety and idempotency. The description adds that it returns name, climate, terrain, population, and orbital data, but these are also captured in the output schema. No additional behavioral traits such as error handling or rate limits are disclosed.

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, front-loaded sentence that gets straight to the point. It contains no redundant information and is easy to parse.

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?

For a simple read tool with one parameter, full schema coverage, an output schema, and strong annotations, the description is complete enough. It provides the essential purpose and input requirement, with no significant gaps.

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?

Schema coverage is 100% with a clear description and example for the id parameter. The description merely repeats that the ID is numeric, adding no significant meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 clearly identifies the resource as a Star Wars planet, distinguishing it from sibling tools like get_film and get_starship. It also lists the returned data fields, making the tool's purpose unmistakable.

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 description clearly implies the tool is for retrieving a planet by its numeric ID, which is the only parameter. However, it does not explicitly mention when to avoid this tool or recommend alternatives (e.g., searching by name). The context is clear enough for selection without exclusions.

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

All swapi toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

The tool set mixes two unrelated domains (Star Wars and Pipeworx data services), which is initially confusing. Within the Pipeworx suite, tools like ask_pipeworx and ask_pipeworx_grounded are clearly differentiated, but some overlap exists (e.g., deep_research vs. compare_entities both do multi-source lookups). Overall, most tools have distinct purposes, but the domain mismatch lowers clarity.

Naming Consistency4/5

All tools use snake_case consistently (e.g., ask_pipeworx, entity_profile, resolve_entity). The naming pattern is mostly verb_noun or descriptive_compound, which is predictable. Minor deviation: some tools start with a verb (ask_pipeworx) while others start with a noun (entity_profile), but the style is uniform.

Tool Count3/5

34 tools is on the high side but not unreasonable for a data-heavy server. However, the set covers two distinct domains (Star Wars and Pipeworx), making it feel bloated. The count could be reduced by separating the domains or pruning rarely-used tools.

Completeness3/5

The Pipeworx side appears comprehensive, covering queries, profiles, comparisons, subscriptions, alerts, and memory. The Star Wars side is incomplete—it lacks tools for vehicles, species, or individual characters (only search_people exists). The overall surface has gaps in one of its two domains.

Resources