Skip to main content
Glama
Sign In

AbaPay

by io.github.investorphem
OverviewDiscussionsAdmin

Transaction History

transaction_history
Read-onlyIdempotent

List recent real transactions for the linked wallet — same data as the AbaPay app's History tab (service, provider, amount, status, tx hash). Read-only, no PIN required. The interactive card's own Next/Previous buttons page through results by re-calling this tool with a different offset — pass offset yourself only when asked for something like "the next page" or "transactions before that" in plain text.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent transactions to return. Defaults to 10, max 25.
offsetNoHow many of the most recent transactions to skip before listing — 0 (default) starts at the newest. Used for paging: offset=10 with the default limit gets the next 10 after the first page.
api_keyNoAbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new context: no PIN is required, the payload matches the app's History tab, and that the UI card pages by re-invoking the same tool. It does not mention rate limits or freshness/latency of the data.

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 sentences, purpose front-loaded in the first clause with the returned-field list as parenthetical support. The second sentence is long with several nested clauses, but each carries actionable paging guidance rather than filler.

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 compensates by enumerating the returned fields (service, provider, amount, status, tx hash); auth is covered by the api_key parameter description and safety by annotations. Paging, scope, and auth are all addressed, leaving nothing essential an agent needs before calling it.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by clarifying the decision boundary for offset (agent should not set it when the card handles paging) rather than merely restating the offset/limit mechanics the schema already documents. It adds no detail on api_key beyond the schema's OAuth note.

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 and resource ('List recent real transactions for the linked wallet') and pins the exact scope by equating it to the app's History tab and enumerating returned fields. 'Real transactions' implicitly separates it from the schedule-oriented siblings (list_schedules, cancel_schedule), so an agent can route without opening the 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?

Gives an explicit conditional for the one ambiguous case: let the interactive card's Next/Previous re-call the tool, and only pass offset manually when the user asks in plain text for 'the next page' or 'transactions before that'. No explicit when-not or sibling-by-name routing (e.g. schedules vs real transactions) is stated, keeping it short of a 5.

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

All AbaPay 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