Skip to main content
Glama

swapi_search_starships

Read-onlyIdempotent

Search Star Wars starships by name to find matching vessel records for Star Wars data lookups.

Instructions

Search Star Wars starships by name.

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": {
      "query": "<query>"
    },
    "name": "swapi_search_starships"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query (e.g. 'falcon')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured fields. The description contributes only the fact that matching is name-based against an open-world catalog; it says nothing about result volume, partial matching, or pagination.

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?

One short sentence with the resource and matching criterion front-loaded; every word earns its place and there is no filler.

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 one-parameter lookup the description is minimally sufficient, and rich annotations remove the need to explain safety. However, with no output schema the agent gets no signal about what a result looks like (full starship records vs. matches, result count, whether exact vs. substring matching applies), which matters for a name search.

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?

Single query parameter is documented at 100% coverage in the schema with an example ('falcon'), so the schema carries the semantics. The description's 'by name' slightly clarifies what the query matches against, but adds no syntax or format detail beyond the schema; baseline 3 applies.

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?

States a specific verb (Search) and resource (Star Wars starships) plus the matching facet (by name), so it is clearly distinct from swapi_get_starship, which retrieves by identifier. It stops short of naming that sibling explicitly, but the verb+resource pairing is unambiguous.

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?

'By name' implies the intended entry point when you have a fuzzy text query rather than an ID, which indirectly differentiates it from swapi_get_starship. There is no explicit when-to-use/when-not-to-use statement or named alternative, so the guidance is only implied.

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