Skip to main content
Glama

swapi_get_planet

Read-onlyIdempotent

Retrieve a Star Wars planet by ID to look up planet details such as Tatooine for a given identifier.

Instructions

Get a Star Wars planet by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "swapi_get_planet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPlanet ID (e.g. 1 for Tatooine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered without prose. The description adds only the ID-keyed lookup scope and says nothing about not-found behavior or what a returned planet record contains.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler, which is proportionate for a one-parameter lookup. It is terse to the point of omitting useful routing information, but no sentence is wasted.

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

Completeness3/5

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

For a trivial single-parameter read, the definition is minimally viable: schema is complete and annotations cover safety. However, with no output schema and no description of the returned planet fields or error behavior, an agent cannot anticipate the response shape.

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 description coverage is 100% and the schema itself supplies a concrete example ('1 for Tatooine'), so parameter meaning is fully documented structurally. The description contributes nothing beyond the schema, making the baseline 3 appropriate.

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

Purpose4/5

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

The description names a specific verb ('Get') and resource ('Star Wars planet') plus the lookup key ('by ID'), so it is unambiguous. It implicitly contrasts with the sibling swapi_search_planets (search vs. direct fetch) but never states that distinction explicitly.

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?

Usage is only implied: 'by ID' suggests you must already have an identifier, which hints that swapi_search_planets is the entry point when you don't. No explicit when-to-use, prerequisites, or alternative routing is given.

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

Deploy Server

Other Tools