Skip to main content
Glama

Ship Details

ship_details
Read-onlyIdempotent

One ship's facts: RSI's specs (career, role, size, crew, dimensions, and the stats its role needs), today's prices in RSI's store, and how often RSI sells it.

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

Input Schema

NameRequiredDescriptionDefault
shipYesA ship name or id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the bar is low. The description adds real context about what is returned and that prices are 'today's' snapshot versus the historical sale data implied by sale_calendar/sale_history. It does not say what happens for an unknown or ambiguous ship name, nor whether the three data blocks are always present.

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?

A single front-loaded sentence with a tight parenthetical enumeration of the returned fields; every clause carries information and nothing is padded.

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?

With no output schema, the description carries the return-value burden and does so by listing the three data blocks. Combined with rich annotations, an agent has enough to call it correctly; the only gap is edge-case behavior for names that do not resolve to exactly one ship.

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 coverage is 100% and the single parameter is documented as 'A ship name or id' with a maxLength. The description's 'One ship's facts' reinforces that the lookup is singular, but adds no detail on name-matching behavior (fuzzy vs exact) or id format beyond what the schema already states. 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?

The description names a concrete resource (one ship) and enumerates the payload: RSI specs (career, role, size, crew, dimensions, role stats), today's store prices, and sale frequency. That is specific enough to separate it from find_ship (search) and compare_ships (multi-ship comparison), though it never names those siblings.

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: 'One ship's facts' signals a single-ship lookup, so an agent can infer it should call this once it already knows the ship. There is no explicit when-to-use, no exclusion (e.g. 'use find_ship if you only have a partial name'), and no mention of alternatives in the sibling set.

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