Skip to main content
Glama

Find a Ship

find_ship
Read-onlyIdempotent

Finds a Star Citizen ship or vehicle by any name or spelling and returns Open Hangar's name for it, its id, maker, role, size, and Store Price. Use it first when a pilot names a ship.

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

Input Schema

NameRequiredDescriptionDefault
nameYesA ship name or id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond them by disclosing fuzzy matching ('any name or spelling') and enumerating the returned fields, which matters because there is no output schema. It omits what happens on a failed or ambiguous match, keeping it at a 4.

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?

Two sentences, both front-loaded: the first covers capability and return shape, the second covers when to reach for it. No redundant restatement of the title or schema.

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

Completeness4/5

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

For a single-parameter read tool with no output schema, the description covers input flexibility and the exact fields returned, which is most of what an agent needs. The remaining gap is edge-case behavior: no statement of what is returned when a name matches nothing or resolves to several ships.

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?

Schema coverage is 100% and the schema documents 'A ship name or id', so the baseline is 3. The description adds meaning beyond that by stating the lookup tolerates any spelling, signalling fuzzy rather than exact matching, which changes how an agent should phrase the value it passes.

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?

States a specific verb and resource (find a Star Citizen ship or vehicle) plus the exact return payload (Open Hangar name, id, maker, role, size, Store Price). The clause 'Use it first when a pilot names a ship' positions it ahead of siblings like ship_details and compare_ships, so an agent can distinguish it without opening other schemas.

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?

'Use it first when a pilot names a ship' gives a clear triggering condition and implies this is the entry point before ship_details or compare_ships. It stops short of naming an explicit when-not case (e.g., when the user already has an id and wants full specs), so it falls just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources