Skip to main content
Glama

MoneyTools payment-safety suite

Spend ledger (Pay Gateway receipts)

ledger_gateway
Read-onlyIdempotent

Totals, by supplier, by day and exceptions for payments relayed by the MoneyTools Pay Gateway for this API key (free; needs X-API-Key). Currency default USD. [served by ledger.moneytools.dev]

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

Input Schema

NameRequiredDescriptionDefault
daysNo
monthNoYYYY-MM
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, and the description adds the context annotations cannot: authentication via X-API-Key, no cost, and a USD currency default. It omits result size/pagination and the time window behavior, which keeps it from a 5.

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 dense sentence front-loads the returned data, then appends access/cost notes and a host annotation in brackets. Every clause carries information, though the parenthetical stacking ('free; needs X-API-Key') is slightly cramped.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only reporting tool with no output schema, the description gives the categories of output but no shape, units, or aggregation granularity, and leaves two of three parameters unexplained. Adequate to attempt a call, insufficient to predict results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%: only 'month' is documented (YYYY-MM). The description clarifies the 'currency' parameter's default (USD), which is genuine added meaning, but 'days' is never explained nor is how 'month' and 'days' interact when both are supplied.

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?

Uses concrete nouns and a clear scope: totals by supplier, by day, plus exceptions, limited to payments relayed by the MoneyTools Pay Gateway for this API key. It is clearly a reporting tool, but it never contrasts itself with sibling reports such as ledger_wallet_report, leaving the agent to infer the boundary.

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?

It implicitly says when the tool applies ('payments relayed by the MoneyTools Pay Gateway for this API key') and adds practical prerequisites (free, needs X-API-Key). There is no explicit exclusion or named alternative for wallet-level vs gateway-level reporting, so selection guidance is only implied.

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