Skip to main content
Glama

Ships for a Role

ships_for_role
Read-onlyIdempotent

Ships that fill a role (cargo, mining, salvage, medical, exploration, combat, and more), cheapest first, with filters for price, size, crew, and Flight Ready. Up to 25 ships.

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

Input Schema

NameRequiredDescriptionDefault
roleYes
sizeNoRSI size: Snub, Small, Medium, Large, Capital
limitNo
max_crewNo
flight_readyNo
max_price_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered. The description adds genuinely new behavior: result ordering is cheapest-first and output is capped at 25 ships. It does not say whether there is pagination/truncation indication when more than 25 match, or whether sort order respects price filters.

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?

One front-loaded sentence naming resource, scope, ordering, and filter axes. The parenthetical role list partly duplicates the schema enum, but it is the only place role semantics are shown in prose.

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 read-only list tool with no output schema, the description covers what is returned at a coarse level but not the record shape or price/basis fields an agent would need to chain into compare_ships or upgrade_price. Adequate but with clear gaps.

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 description coverage is only 17%, so the description carries real weight: it names the price, size, crew, and Flight Ready filters and the 25-item cap, effectively documenting five of six parameters. It still doesn't state filter interaction (AND semantics) or that the cap silently truncates.

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 and resource: returns ships matching a role, enumerates the role set, and discloses ordering (cheapest first). An agent can tell this is a role-based browse rather than a lookup like find_ship or ship_details, though it never names a sibling.

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 implied by the phrasing 'Ships that fill a role ... cheapest first, with filters' – it is the browse-by-role path. There is no explicit when-to-use versus compare_ships/find_ship, and no statement of when this returns nothing useful.

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