Skip to main content
Glama

Ship Rarity

ship_rarity
Read-onlyIdempotent

A ship's or item's rarity tier, with its reason and sources, only when Open Hangar's research proves it. No tier means it isn't proven rare.

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": "ship_rarity"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA ship or item name

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description goes beyond them by disclosing the negative case — an absent tier explicitly means 'not proven rare' rather than an error or empty result — and by stating that reason and source provenance accompany the tier. That is meaningful behavioral context an agent could not infer from annotations.

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?

Two short sentences with no filler, and the core semantics (proof-gated result, absent tier meaning) are front-loaded. Phrasing is slightly awkward ('only when Open Hangar's research proves it') but costs nothing.

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 must convey what comes back, and it does: a tier plus reason and sources, or nothing when unproven. For a single-parameter read-only lookup that is essentially complete; only name-matching behavior is left unstated.

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% with a single well-described 'name' parameter, so the schema carries the load. The description adds only a slight nuance, confirming that item names as well as ship names are accepted; it gives no resolution or matching behavior for ambiguous names.

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-less but unambiguous resource: returns a rarity tier for a ship or item, plus the reason and sources behind it. This is narrow enough to distinguish it from general lookups like ship_details or find_ship, though the description never names those siblings explicitly.

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?

Use is implied (call it to learn whether something is proven rare), and the 'only when research proves it' clause gives a useful selection rule. However, it offers no explicit guidance on when to prefer this over ship_details or find_ship, which likely also surface ship information.

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