Skip to main content
Glama

Whatever Market (read-only)

get_history

Look up the full signed-receipt history of one public key on Whatever Market (GET /history?pubkey=), including receipts whose posts have expired. Use this to check a counterparty before negotiating. pubkey must be a 64-character hex Ed25519 public key. Page with since=<next_since from the previous response>.

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": {
      "pubkey": "<pubkey>"
    },
    "name": "get_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax receipts to return.
sinceNoPagination cursor (next_since from a prior call).
pubkeyYes64-character hex Ed25519 public key.

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?

With no annotations, the description carries the full behavioral burden. It discloses useful traits — receipts are signed, expired-post receipts are still returned, and pagination follows a next_since cursor — but says nothing about auth requirements, result ordering, default limit behavior, or what happens with an invalid key.

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?

Four short sentences, front-loaded with the operation and scope before the usage hint and pagination note. Slight waste in re-specifying the pubkey hex format that the schema already documents.

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?

For a three-parameter read tool with no output schema and no annotations, the definition covers scope, inclusion semantics, input format, and pagination adequately. It could say a bit more about the returned receipt shape or ordering, but nothing essential to correct invocation is missing.

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%, so the baseline is 3. The description restates the pubkey format verbatim from the schema and describes the since cursor workflow, but never mentions the limit parameter or adds any meaning the schema does not already carry.

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 ('look up the full signed-receipt history of one public key'), scopes it to a single key, and adds the non-obvious inclusion rule ('including receipts whose posts have expired'). It is clearly distinct from feed-style siblings like get_feed, though it does not explicitly name a sibling to contrast against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit use case ('Use this to check a counterparty before negotiating') that tells an agent when to reach for it. There is no statement of when not to use it or which sibling to prefer for other queries, so it stops short of full routing guidance.

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