Agent Paywire library

Read support and paid-API details

get_support_info

Read-onlyIdempotent

Return the voluntary support descriptor: donation methods (Bitcoin on-chain, Lightning BOLT12, USDC on EVM networks and Solana) with addresses, suggested sat amounts, and the paid_api block (L402 over Lightning, 100 sats for 100 credits, valid 30 days). Calling it never sends money or creates an invoice, and the data stays free whether or not anyone pays. Use it when a user wants to tip or asks how to pay for the API. Use get_trust_checklist for error codes, rate limits, and stable URLs. Use get_protocol_facts for third-party payment protocols. Free, no auth.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`methods`	Yes
`voluntary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "methods": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "voluntary": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "voluntary",
+    "methods"
+  ],
+  "type": "object"
+}

First observedOct 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true. The description adds non-redundant behavior: calling it never sends money or creates an invoice, the data is free regardless of payment, and it requires no auth. That is meaningful beyond the annotations, though return/pagination shape is left to the output schema.

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?

Front-loads the core purpose, then the behavioral guarantee, then the two sibling routes and auth note. Every sentence carries a distinct fact, though the parenthetical payment-method list is somewhat dense for a selection-focused description.

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?

An output schema exists, so return-value details need not be spelled out; the description still covers non-mutation, no-auth, and where adjacent needs live. Sufficient for an agent to select and invoke it correctly, with only minor room to note freshness or idempotency beyond annotations.

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?

The tool takes zero parameters, so the baseline is 4; schema description coverage is 100% and there is nothing for the description to compensate for. No parameter guidance is needed or missing.

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 ('Return the voluntary support descriptor') and enumerates exactly what it contains: donation methods (Bitcoin on-chain, Lightning BOLT12, USDC on EVM/Solana) with addresses and amounts, plus the paid_api block. An agent can distinguish it from the other get_* siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('when a user wants to tip or asks how to pay for the API') and routes two adjacent needs elsewhere: get_trust_checklist for error codes/rate limits/stable URLs, get_protocol_facts for third-party payment protocols. When-to-use and alternatives are both named.

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

All Agent Paywire library tools Inspect

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

Need Help?