Skip to main content
Glama
Sign In

SingIt x402

by app.singitai
OverviewDiscussionsAdmin

Get receipts

get_receipts
Read-onlyIdempotent

Your recent receipts, newest first: for each, its id, time, model, USDC charged, tokens and the upstream reference (kind charge, this key only), or the account's top-ups and refunds with their transaction and network. Read-only; page back with before. Free, but needs your API key.

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

Input Schema

NameRequiredDescriptionDefault
kindNocharge (default): what this key spent; topup: money added to the account; refund.
limitNoHow many, newest first. Defaults to 10.
beforeNoOnly entries older than this receipt id: pass the last id of the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses meaningful behavior: results are newest first, charges are scoped to the current key, top-ups/refunds include transaction and network details, pagination uses `before`, and the call requires an API key despite being free. These are useful operational details an agent would not get from annotations alone.

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?

The description is two dense but well-structured sentences. It front-loads the core purpose and packs return fields, pagination, auth, and cost into minimal space without waste.

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 burden of explaining return contents, and it does so by listing the key fields and distinguishing charge records from top-ups/refunds. It also covers pagination, read-only behavior, and API-key requirements, making it complete for correct invocation.

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 `kind`, `limit`, and `before` thoroughly. The description reinforces pagination and the charge/topup/refund distinction but does not add substantially more than the schema provides, making 3 the appropriate baseline.

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 clearly states that it returns recent receipts, newest first, with specific fields and distinct handling for charge/topup/refund records. It is specific about the resource and output shape, though it does not explicitly contrast itself with siblings such as get_balance.

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?

It gives clear context for reading receipts and explicitly explains pagination via `before`, plus notes that the tool is free but requires an API key. It does not name alternatives or state when not to use it, so it stops short of full when-to-use guidance.

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

All SingIt x402 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