Skip to main content
Glama

recharge

by io.usefulapi
OverviewDiscussionsAdmin

List addresses

recharge_list_addresses
Read-only

List customer addresses with optional filters (customer, ids, created/updated date ranges). Returns { addresses }. Pagination is cursor-based: pass limit (default 50, max 250) and read next_cursor / previous_cursor from the response. IMPORTANT: when paging with cursor, Recharge accepts ONLY limit alongside it — omit every other filter on cursor requests. Recharge REST: GET /addresses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated list of address ids to fetch.
limitNoMax results per page (1-250, default 50).
cursorNoPagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests.
customer_idNoFilter by customer id.
created_at_maxNoFilter to addresses created on/before this date (ISO 8601).
created_at_minNoFilter to addresses created on/after this date (ISO 8601).
updated_at_maxNoFilter to addresses updated on/before this date (ISO 8601).
updated_at_minNoFilter to addresses updated on/after this date (ISO 8601).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations give readOnlyHint. Description adds pagination details, cursor restriction, and REST endpoint. No contradiction.

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?

Very concise 4 sentences. Front-loaded purpose, then filter summary, pagination details, and important cursor warning in bold. No fluff.

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?

Covers purpose, filters, pagination, cursor restriction, REST endpoint. Lacks return object structure, but with 8 optional params, it is fairly complete.

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 coverage 100% with detailed descriptions. Description summarizes filters but adds little beyond schema. Baseline 3.

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?

Description clearly states verb 'List' and resource 'customer addresses' with optional filters. Siblings are for different entities (charges, customers, etc.), so no confusion.

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?

Provides explicit cursor usage rule: omit other filters with cursor. No explicit when-not-to-use, but context makes it clear for different resources.

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

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