x402 agent toolkit: service finder, payment safety, Solana & web tools

by dev.workers.moneytools.x402-pay-precheck

MoneyTools partner program info (free)

partner_program_info

Read-only

Free. How to earn by recommending MoneyTools (we run this server): join steps, ref= attribution, 2-tier terms (20% of net revenue for 12 months, +5% tier 2, not MLM), required disclosure. No income guaranteed. [served by tools.moneytools.dev]

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them: the content is a static info payload served by tools.moneytools.dev, it includes an income disclaimer ('No income guaranteed'), and it clarifies the program is not MLM.

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 'Free.' and then the purpose, and every clause carries information. It is dense and slightly list-like (parenthetical terms, host tag), but no sentence is filler for a static info tool.

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?

For a parameterless, read-only lookup with no output schema, the description covers the important question: what the returned content contains (join steps, attribution format, tier terms, required disclosure) and its caveats. Nothing further is needed to invoke it correctly.

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?

With zero parameters there is nothing for the description to disambiguate, so the baseline applies. It still explains the ref=<mt-code> attribution convention referenced in the program terms, which is terminology the agent may need when relaying the answer.

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?

The description states a specific verb+resource: it returns instructions for earning by recommending MoneyTools, and enumerates what the answer covers (join steps, ref attribution, 2-tier terms, disclosure). No sibling tool in the list covers referral/partner economics, so the agent can select it unambiguously.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'How to earn by recommending MoneyTools' signals the topic, and 'Free' signals cost, but there is no explicit 'call this when the user asks about referrals/affiliate earnings' or any exclusion. With no near-alternatives among siblings the risk is low, but guidance is inferential.

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

All x402 agent toolkit: service finder, payment safety, Solana & web tools 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?