FortFi Treasury MCP

create_payment_product

Create a persistent product checkout link (/pay/p/{slug}). Each visit mints a fresh payment request. One webhook endpoint receives paid events for all products.

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": {
      "walletMappingId": "<walletMappingId>",
      "name": "<name>"
    },
    "name": "create_payment_product"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Product display name
`slug`	No	Optional URL slug (auto-generated if omitted)
`imageUrl`	No	HTTPS product image URL for checkout branding
`amountUsd`	No	Price in USD/USDC
`description`	No	Checkout subtitle shown to buyers
`merchantSiteUrl`	No	Merchant homepage for checkout branding (optional)
`walletMappingId`	Yes	USDC collection vault id
`amountSmallestUnit`	No	Alternative: amount in token smallest units
`successRedirectUrl`	No	HTTPS buyer redirect after pay (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations at all, this description does real work: it discloses the canonical link format, that every visit spawns a new payment request (a non-obvious runtime behavior), and that a single webhook endpoint aggregates paid events across all products. What it omits is equally behavioral: permission/auth requirements, what happens on slug collision, and whether amounts can be changed after creation.

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, front-loaded with the core action and URL shape, then behavior, then webhook implication. No filler and nothing redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter creation tool with no annotations and no output schema, the definition covers purpose and link behavior but never says what is returned (product id, full URL, or slug) — information the agent needs after a successful create. Wallet/vault prerequisites for walletMappingId are also unaddressed.

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 100%, so every parameter is already documented, and the description only indirectly illuminates one of them by showing that slug appears in the URL path. It adds no guidance on the amountUsd vs amountSmallestUnit alternative, which is the one genuinely ambiguous parameter pair.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb + resource ('Create a persistent product checkout link') with the concrete URL shape (/pay/p/{slug}), which makes it easy to distinguish from one-off request tools like create_payment_request. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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?

'Persistent' and 'each visit mints a fresh payment request' implicitly signal this is for reusable product pages rather than single charges, which hints at when to prefer it over create_payment_request or create_checkout_session. There is no explicit when-to-use/when-not-to-use statement or prerequisite guidance (e.g., that a walletMappingId vault must exist first).

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

All FortFi Treasury MCP 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?