Skip to main content
Glama

Sale History

sale_history
Read-onlyIdempotent

When RSI has sold a ship since November 2021: each sale window with its price and whether it was a warbond, how often it sells, and its usual price.

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

Input Schema

NameRequiredDescriptionDefault
shipYesA ship name or id

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, closed-world and non-destructive, so safety is covered. The description adds genuinely new behavioral context that annotations cannot: the coverage window (November 2021 onward) and the exact shape of the returned facts, which matters because there is no output schema.

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?

One compact sentence with the temporal scope front-loaded and the returned fields listed after the colon; there is no filler. The phrasing 'When RSI has sold a ship since November 2021' is slightly awkward as an opener but reads cleanly.

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 enumerating the fields the agent will receive. The only real gap is not saying what a ship with no recorded sales returns, which is minor for a single-parameter read.

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?

The single `ship` parameter is fully described in the schema as 'A ship name or id' at 100% coverage, so the baseline is 3. The description adds nothing about accepted name formats, case sensitivity, or what happens with an ambiguous name.

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?

It names the resource (a specific ship's sale history) and enumerates what comes back — sale windows, price, warbond flag, frequency, usual price — so an agent can tell this is a per-ship historical lookup, not a current-store query. It never explicitly contrasts itself with sale_calendar or store_now, so it stops 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?

Usage is only implied: the temporal bound 'since November 2021' signals this is a backward-looking query for one ship, which distinguishes it in spirit from a live store check. There is no explicit 'use this when…' clause and no named alternative for someone who wants forward-looking sale dates.

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