New Runtime public records

List New Runtime paid tools

list_paid_tools

Read-onlyIdempotent

Use when the free tools left a question open and you can pay per call: lists New Runtime's x402 tools (find the primary source of a claim $0.10, rumour check $0.40, research bundle, prior-coverage check) with endpoint, USDC price, input example, when you are charged, and how to pay without an account. Free to call.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`tools`	Yes	Paid tools.
`how_to_pay`	Yes	How to pay per call over x402 without an account.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "how_to_pay": {
+      "description": "How to pay per call over x402 without an account.",
+      "type": "string"
+    },
+    "tools": {
+      "description": "Paid tools.",
+      "items": {
+        "properties": {
+          "charged": {
+            "description": "When you are charged."
+          },
+          "endpoint": {
+            "description": "HTTPS endpoint; POST a JSON body."
+          },
+          "input_example": {
+            "description": "Example request body."
+          },
+          "name": {
+            "description": "Tool name."
+          },
+          "price_usd": {
+            "description": "Price in USD (USDC)."
+          },
+          "returns": {
+            "description": "What the tool returns."
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "how_to_pay",
+    "tools"
+  ],
+  "type": "object"
+}

AddedSep 25, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety coverage is done. The description adds value the annotations cannot: free to call, when charges apply, and that payment works without an account — key facts for an agent deciding whether it can use paid endpoints.

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?

One front-loaded sentence with the trigger first and the itemized contents after. The parenthetical price list is dense but each item provides concrete cost information an agent needs; slightly long for a no-argument listing tool.

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 an output schema covering the return shape, the description only needs to convey scope, cost model, and access requirements — and it covers all three, including the accountless payment path. Nothing an agent needs to decide whether to call 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?

Zero parameters, so there is nothing to disambiguate; baseline is 4. The description does not need to describe inputs and correctly doesn't invent any.

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 ('lists New Runtime's x402 tools') and enumerates the concrete contents (endpoint, USDC price, input example, charge timing, payment path). No sibling in the list does anything similar, so it is distinguishable 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 Guidelines5/5

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

Gives an explicit trigger ('Use when the free tools left a question open and you can pay per call') and a counter-signal that the tool itself is free, so the agent knows both when to reach for it and that calling it carries no cost.

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

All New Runtime public records tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?