Agent Paywire library

Get checked protocol facts

protocol_facts

Read-onlyIdempotent

Return source-cited facts for agent payment protocols: spec URL, HTTP status codes and headers, payment rail, networks, facilitators, client libraries, pay flow and an example. Every fact carries its source URL and verified_at; null means the cited page does not state it. Omit id for all nine protocols in a protocols array (about 23 KB); pass id for that one protocol's object only. Use this for how a protocol works; use search_library to find papers or docs about it, and get_support_info for this site's own paid L402 API. An id outside the enum is rejected as invalid input. Free, no auth.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	Lowercase protocol id from the enum, e.g. l402. Set it to get one protocol object (smaller response); omit it to get every protocol in a protocols array.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`protocols`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / id / description

Previous value: -"Protocol id. Example: l402. Omit for every protocol."New value: +"Lowercase protocol id from the enum, e.g. l402. Set it to get one protocol object (smaller response); omit it to get every protocol in a protocols array."

Changed3 schema fields changedOct 20, 2026

changedInput schema / properties / id / description

Previous value: -"Protocol id, for example l402 or x402."New value: +"Protocol id. Example: l402. Omit for every protocol."

addedInput schema / properties / id / enum

Added value: +[
+  "l402",
+  "bolt12",
+  "bip21",
+  "nwc",
+  "x402",
+  "mpp",
+  "ap2",
+  "acp",
+  "ucp"
+]

changedOutput schema / (root)

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

First observedOct 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds real behavioral context beyond them: null means the cited page does not state the fact, every fact carries source URL and verified_at, the all-protocols response is about 23 KB, out-of-enum ids are rejected as invalid input, and no auth is required.

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-loaded with purpose and tightly packed; the field enumeration is long but tells the agent what is inside without opening the output schema. Every sentence carries information, though the field list and the schema overlap slightly.

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?

Given a single optional enum parameter, an output schema, and full annotation coverage, the description still supplies the null semantics, response size, auth status, and sibling routing an agent needs. Nothing material is missing.

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 omit-vs-set semantics of id are already documented; the description largely mirrors that. It does add the quantified response size (~23 KB for nine protocols) and the invalid-enum rejection behavior, which the schema does not state.

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?

Opens with a specific verb and resource ('Return source-cited facts for agent payment protocols') and enumerates exactly what a fact contains. It is immediately distinguishable from siblings like search_library and get_support_info, which the description itself names.

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?

Explicit routing is given: use this for how a protocol works, search_library to find papers or docs about it, get_support_info for the site's own paid L402 API. It also states the two calling modes (omit id for all nine, pass id for one) so the agent knows when to pick which.

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?