Skip to main content
Glama

get_module_purchase_history

Retrieves Elite Dangerous module purchase history from journal events, returning real prices, stations, systems, and timestamps to compare current outfitting costs against what you paid.

Instructions

Your module purchase history from journal events (ModuleBuy/ModuleSell/ModuleRetrieve).

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

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_module_purchase_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
journal_dirNo
module_queryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the data source (journal events) and the fields returned (real prices, stations, systems, timestamps), which is above-nothing. However, it omits behavior such as what happens when journal_dir is unset, whether results are cached/paginated, or how missing events are handled for a read-only query.

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, front-loaded with the resource and then the payoff. No filler; only minor room to fold the use case into a tighter statement.

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-shape explanation is unnecessary, and the description covers that adequately. But for a tool with two fully undocumented parameters and no annotations, the definition leaves the agent guessing on invocation details.

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% for two parameters (journal_dir, module_query), and the description adds no meaning to either — it never explains what module_query accepts (exact name, partial, ID) or what journal_dir overrides. The event names hint at filtering but do not document the parameter.

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+resource (retrieve module purchase history) and names the exact journal event types (ModuleBuy/ModuleSell/ModuleRetrieve) that constitute the data. It is naturally distinguishable from get_ship_purchase_history by resource, though it never explicitly says so.

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?

"Useful for comparing current outfitting prices vs what you actually paid" implies a use case but gives no explicit when-to-use/when-not or named alternative (e.g. get_station_outfitting for current prices). Guidance is inferable rather than stated.

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