Skip to main content
Glama
Pirate Ship MCP Server

Pirate Ship MCP Server

List receipts

list_receipts
Read-onlyIdempotent

Lists payments made to Pirate Ship, newest first, with status, date range, search and pagination filters to review account charges.

Instructions

Payments made to Pirate Ship, newest first; get_receipt shows one.

The Reports, Receipts table: each payment the account made (card, PayPal, bank) with its status, description and total in US dollars. Pass receipt_id to get_receipt for the labels it paid for.

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

Input Schema

NameRequiredDescriptionDefault
sortNoOrder by date.newest
limitNoRows per page, 1 to 100.
offsetNoRows to skip: the next page starts at offset + limit while it is below total.
searchNoFree text, as in the report's search box.
statusNoPayment status as the table shows it.
to_dateNoLast day, YYYY-MM-DD, included.
from_dateNoFirst day, YYYY-MM-DD, in your timezone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.4
    • addedInput schema / properties / limit / description
      Added value: +"Rows per page, 1 to 100."
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip: the next page starts at offset + limit while it is below total."
    • addedInput schema / properties / sort / description
      Added value: +"Order by date."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent safety, so the description's job is to add context -- and it does: newest-first default ordering, the payment methods covered (card, PayPal, bank), the fields each row carries (status, description, total in USD), and the fact that it mirrors the Reports > Receipts table. Pagination and limits are left to the schema, which is fine given full coverage.

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 compact sentences that lead with the resource and the ordering, then add the table mapping and the sibling handoff. The 'Reports, Receipts table' phrasing is slightly awkward but still readable and nothing is padding.

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?

No output schema exists, and the description compensates by naming the row fields (status, description, total) and the currency. Paging, limits, and filters are fully documented in the schema. Slightly more on what an empty result means or on total-row counts would push this to a 5.

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% and each of the seven parameters has a precise description, so baseline 3 applies. The description only reinforces the default sort ('newest first'); the mention of receipt_id is not a parameter of this tool and could momentarily confuse an agent into thinking it is.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Payments made to Pirate Ship'), the default ordering ('newest first'), and explicitly points to get_receipt as the single-item counterpart. An agent can distinguish this from list_transactions, list_refunds, and get_receipt without opening a schema.

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?

'get_receipt shows one' gives a clear when-to-use-this-vs-that signal and explains the receipt_id handoff. It stops short of saying when to prefer list_receipts over the nearby list_transactions or list_refunds siblings, which is the main remaining ambiguity for an agent browsing payment data.

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