Skip to main content
Glama
Sign In

McpStamp Statement of Account

by io.github.theluckystrike
OverviewDiscussionsAdmin

Age the open invoices

statement_aging

Age open invoices into 0-30, 31-60, 61-90 and over 90 days past DUE date at a date, per client and currency, with the invoices themselves. Free. statements_report rolls up the whole book instead.

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

Input Schema

NameRequiredDescriptionDefault
as_ofNoAge the invoices as at this date, YYYY-MM-DD. Defaults to today
limitNoMaximum invoice rows returned, default and ceiling 2000
clientNoOne client id or name. Omit to age every client in the books
currencyNoOnly this currency. Omit for every currency, each aged separately

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations provide no real safety profile (all hints false/absent), so the description carries the burden. It adds useful facts: buckets are based on DUE date, invoices themselves are returned, and the tool is free. However, it does not state whether this is a pure read/report operation, whether any state changes occur, or any auth/rate-limit implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two efficiently written sentences front-load the core aging logic and output, then close with a clear sibling distinction. No filler or redundant restatement of the title.

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 list/report tool with no output schema, the description conveys the essential return content ('the invoices themselves'), the aging bucket boundaries, and the main alternative. It could be more complete about output structure, ordering, or limit behavior, but the key calling context is present.

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 description coverage is 100%, so the schema already documents as_of, limit, client, and currency. The description reinforces the client/currency/date dimensions but adds no meaning the schema does not already provide.

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?

The description specifies the operation ('Age open invoices'), defines the output (buckets by days past due, per client/currency, with invoices themselves), and names the distinguishing sibling (statements_report), making the tool's purpose immediately clear.

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?

The description explicitly contrasts itself with statements_report, telling the agent to use the sibling when the whole book is needed in rolled-up form. It also mentions the per-client/currency granularity, but it doesn't address other siblings like statement_build or statement_text.

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

All McpStamp Statement of Account toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources