Skip to main content
Glama

My recorded payments

portal_payments_list
Read-onlyIdempotent

Payments Barmaan has recorded as received from you, newest first: date, amount in the original currency, method (cash / bank / exchange), prepayment flag and the invoice it was applied to when known. Filter by currency or date range. Page with next_cursor. These are records, not an online payment.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNo
cursorNoValue of next_cursor from the previous page.
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: newest-first ordering, the set of returned fields, and the clarification that these are records rather than an online payment flow.

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 dense sentences, front-loaded with what the tool returns and followed by filtering and paging. Nearly every clause carries information; only the final disclaimer is arguably redundant with the opening framing.

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?

With no output schema, the description helpfully enumerates the returned fields and ordering, and it covers filtering and pagination for a 5-parameter read tool. The only real gap is the absence of page-size and date-format semantics, which the schema partly supplies.

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 only 20%, so the description must carry weight; it does map 'currency' and 'date range' to the to/from/currency parameters. However, it says nothing about the limit cap of 25, the default page size of 10, or the date format, leaving several parameters to be discovered purely from 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 gives a concrete verb+resource ('Payments Barmaan has recorded as received from you') and even enumerates the returned fields, so an agent knows exactly what data comes back. It does not name a sibling tool, but the closing line 'These are records, not an online payment' delimits the scope against an obvious misreading.

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 tells the agent how to narrow results ('Filter by currency or date range') and how to paginate ('Page with next_cursor'), which is practical invocation guidance. It never states when to prefer this over an invoices or order tool, so the choice among siblings remains inferred.

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