Skip to main content
Glama

Compare Ships

compare_ships
Read-onlyIdempotent

Two to four ships side by side, with a focus: general, cargo, combat, or racing. Price per SCU shows only for cargo ships with the cargo focus.

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

Input Schema

NameRequiredDescriptionDefault
focusNo
shipsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 genuinely useful output behavior beyond that: price-per-SCU appears only for cargo ships under the cargo focus, which warns the agent that results vary by focus. It stops short of describing other output fields or what happens when focus is omitted.

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 tight sentences with the core capability front-loaded and the conditional output caveat second. No filler or redundant restatement of the title.

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 simple two-parameter read-only tool with no output schema, the description covers count bounds, focus options, and one output rule. It is still incomplete on the identifier format for the required 'ships' array and on default focus behavior, both of which an agent needs to call correctly on the first try.

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 0%, so the description must carry the semantic load. It restates the 2-4 ship bound and the focus enum already present in the schema, but it does add real meaning: focus selects the comparison dimension and changes which metrics are returned. It says nothing about what form the 'ships' entries should take (names, slugs, IDs), leaving the most important parameter ambiguous.

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 states a specific verb and resource ('two to four ships side by side') with the comparison dimensions enumerated. It is clearly distinguishable from lookups like ship_details or find_ship, though it does not name a sibling to contrast against.

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 'two to four ships side by side' and the focus options, so an agent can infer this is the tool for side-by-side comparison rather than a single-ship lookup. However, there is no explicit when-to-use guidance, no mention of the default focus, and no stated alternative for single-ship queries.

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