LeadFuzion Agent Store

Buy a lead package

buy_package

Buy one LeadFuzion lead package (one item_id) at its listed price. Call get_package_quote first: it is free and shows the price. Without payment this returns the price and how to pay (x402 USDC on Base, MPP card, or MPP Tempo), and nothing is charged. If your client cannot pay inside MCP, pay at the HTTPS URL given and pass the order_token back here.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item_id": "<item_id>"
    },
    "name": "buy_package"
  }
}

Input Schema

Name	Required	Description
`buyer`	No	Who is buying: person or company name plus a contact. Recorded with the order.
`item_id`	Yes
`purpose`	No	What the leads will be used for. Recorded with the order.
`order_token`	No	Proof of a purchase already paid at the HTTPS endpoint or in an earlier call. Redelivers that order; no charge, no attestation needed. Valid 7 days.
`accept_terms`	No	Must be true: you accept the terms at terms_url.
`terms_version`	No	terms_version from get_package_quote

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already flag this as non-read-only, non-idempotent, and open-world, and the description usefully adds that an unpaid call charges nothing and merely returns price plus payment options. The x402/USDC/MPP payment methods and the 7-day order_token redelivery semantics add real behavioral context. It stops short of covering failure modes such as an unavailable item or what a successful paid response contains.

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?

Three tight sentences: the action first, then the prerequisite, then the fallback payment flow. No filler and the most decision-relevant information leads.

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 six-parameter purchase tool with no output schema, the description covers the free-preview path and the paid path well enough to call it correctly. The main remaining gap is what a successful charged purchase returns beyond the order being recorded.

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 is 83%, so buyer, purpose, order_token, accept_terms, and terms_version are already documented in the schema. The description reinforces the order_token loop and ties terms_version to get_package_quote, but adds little meaning beyond the existing field descriptions for a mutation tool with a high-coverage schema.

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, resource, and unit constraint: "Buy one LeadFuzion lead package (one item_id) at its listed price." An agent can immediately distinguish this purchase action from the sibling quote and list tools 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 prerequisite ("Call get_package_quote first: it is free and shows the price") and a concrete alternative path when the client cannot pay in-band (pay at the HTTPS URL and pass order_token back). The selection logic between the flows is spelled out rather than implied.

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

All LeadFuzion Agent Store 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?