Skip to main content
Glama

get_ship_purchase_history

Retrieve your actual ship purchase history from journal events to compare what you paid against current market prices and spot discounts.

Instructions

Your actual ship purchase history from journal events (ShipyardBuy/ShipyardSell).

Returns real purchase prices, stations, systems, timestamps — useful for comparing current market prices vs what you actually paid, spotting discounts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ship_purchase_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
ship_queryNo
journal_dirNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It reveals the journal event types and returned fields (prices, stations, systems, timestamps), but says nothing about read-only nature, what happens when no journal files exist or journal_dir is omitted, or the cost of scanning journals. Missing-data behavior is a notable gap for a history-scanning tool.

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 tight sentences with the data source front-loaded and the value proposition second. Minor wasted phrasing in 'Your actual' and the trailing clause, but nothing extraneous.

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?

An output schema exists, so return values need not be explained, and the description adequately frames what data comes back. However, for a tool with a fully undocumented parameter set and no annotations, it leaves gaps around filtering behavior and journal source resolution.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and neither parameter is mentioned in the description. 'ship_query' (a filter by ship name? fuzzy match?) and 'journal_dir' (required location of logs, or optional override?) remain ambiguous, and the description does nothing to compensate.

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 specific verb and resource (ship purchase history) and discloses the data source explicitly (journal events ShipyardBuy/ShipyardSell), which distinguishes it from live-market siblings like get_station_shipyard. It does not explicitly name a sibling alternative, so it falls just short of a 5.

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?

It gives an implied use case — comparing current market prices against what you actually paid, spotting discounts — but never states when to prefer this over get_station_shipyard or find_ship, nor any exclusions. Usage is inferable rather than instructed.

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