IDPHANTOM MCP Server

Submit a payment

submit_payment

DestructiveIdempotent

Broadcast an authorized payment intent to settle funds on Base; retries return the already-submitted transaction hash instead of rebroadcasting.

Instructions

Broadcast an authorized payment intent through IDPHANTOM. The platform relays the on-chain transaction; exactly one broadcast per intent is enforced server-side (retries return the already-submitted transaction hash). This is the step that settles funds.

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": {
      "payment_intent_id": "<payment_intent_id>"
    },
    "name": "submit_payment"
  }
}

Input Schema

Name	Required	Description	Default
`payment_intent_id`	Yes	Authorized payment intent ID to broadcast and settle.

Output Schema

Name	Required	Description	Default
`content`	Yes
`isError`	No	True when the API call failed; text carries { error: { code, message } }.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.6Oct 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations (destructive, idempotent, openWorld), the description discloses the concrete idempotency behavior: exactly one broadcast per intent and retries returning the already-submitted transaction hash. That is genuinely useful operational detail an agent could not derive from idempotentHint=true alone. It could still say more about failure/error behavior, but it adds real value.

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 with no redundancy, and the core action plus settlement outcome are front-loaded. Every sentence carries information.

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 present and annotations covering the safety profile (readOnly=false, destructive, idempotent), the description only needs to frame the action and its consequence, which it does. Nothing essential for correct invocation is missing.

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?

Only one parameter, already 100% covered by the schema ('Authorized payment intent ID to broadcast and settle'). The description's phrasing mirrors the schema and adds no new semantics such as ID format or where the ID comes from, so baseline 3 applies.

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 (broadcast) and resource (authorized payment intent) plus the concrete outcome ('this is the step that settles funds'). It clearly occupies a distinct position in the quote → authorize → submit → verify chain rather than overlapping the siblings.

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

Usage Guidelines4/5

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

The description scopes usage to an 'authorized payment intent,' which implicitly means it follows authorize_payment, and adds the settlement context. It does not, however, explicitly name when-not to use it or contrast it directly with verify_payment, so the routing is implied rather than stated.

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

Deploy Server