Skip to main content
Glama

Tally by Outpost

List sales

list_sales
Read-onlyIdempotent

Payments newest first, each with its amount as charged and in US dollars, whether it is linked to a visitor, how (method and confidence), and why not when it isn't. Filter to unlinked payments or refunds.

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

Input Schema

NameRequiredDescriptionDefault
showNoWhich payments (default all).
siteNoThe site's id. Optional: the API key's site is the one read.
limitNoRows at most (default 50).
cursorNoThe next_cursor of the previous page, to read on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, non-destructive read, so the description needn't restate safety. It adds real behavior beyond that: default sort order, the dual-currency amount representation, the linkage/method/confidence fields, and the explanation of why a payment is unlinked. Pagination behavior is the main omission.

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, front-loaded with the ordering and row shape, then the filtering option. Every clause carries content; only the dual-currency phrasing is slightly dense and could parse ambiguously at first read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 well, enumerating each column an agent will receive and how unlinked rows are explained. For a read-only listing tool with fully documented parameters, nothing essential for 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 all four parameters are already documented with meanings, enums, patterns, and defaults. The description only re-touches the show filter ('unlinked payments or refunds') and says nothing about site, limit, or cursor, so it adds no meaning beyond the schema.

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 states the resource (payments/sales) and its ordering (newest first), plus the per-row content: amount as charged, USD amount, linkage status, link method with confidence, and failure reason. It is clear what the tool returns, though the listing verb is only implied rather than stated, and it does not name a sibling it contrasts with.

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?

The closing sentence 'Filter to unlinked payments or refunds' implies when the show filter is relevant, and the newest-first ordering hints at recency use cases. But there is no explicit when-to-use, when-not-to-use, or pointer to any alternative among the many sibling analytics tools.

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