SpherePay MCP Server

Overview Schema Source Related Servers Discussions Admin

submit_cctp_offramp

Submit a CCTP burn transaction for off-ramp redemption. Provide the source chain (Sei or Noble), burn transaction hash, and payout transfer ID to initiate the cross-chain transfer payout.

Instructions

Submit a CCTP (Cross-Chain Transfer Protocol) burn transaction for off-ramp redemption. source_chain: 'sei' or 'noble'. source_transaction_hash: the burn transaction hash from the source chain. transfer_id: the payout/transfer ID (format: payout_...).

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": {
      "source_chain": "<source_chain>",
      "source_transaction_hash": "<source_transaction_hash>",
      "transfer_id": "<transfer_id>"
    },
    "name": "submit_cctp_offramp"
  }
}

Input Schema

Name	Required	Description	Default
`source_chain`	Yes
`source_transaction_hash`	Yes
`transfer_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1Mar 21, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose all behavioral traits. It only says 'Submit' without explaining side effects, idempotency, confirmation steps, or whether the transaction is actually sent to the network. This leaves the agent guessing about the tool's impact.

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?

Description is two short sentences with no wasted words. Parameter explanations are inline and front-loaded. Every sentence adds value.

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?

Given the output schema exists (not shown), return values need not be described. However, the tool is a submission action and lacks prerequisites (e.g., having a burn transaction) or error conditions. It is minimally adequate but not complete.

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?

Schema has 0% description coverage, so the description must compensate. It explains source_chain as 'sei' or 'noble' (though no enum in schema), source_transaction_hash as the burn hash, and transfer_id with format 'payout_...'. This adds meaningful usage hints beyond the bare 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?

Description clearly states the action 'Submit a CCTP burn transaction for off-ramp redemption' with a specific verb and resource, distinguishing it from sibling tools like execute_transfer or get_transfer.

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?

Description implies usage when a burn transaction is ready for off-ramp redemption, but does not explicitly state when to use this tool versus alternatives (e.g., execute_transfer) or provide any exclusions.

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