Skip to main content
Glama
verifystack-x402-mcp

verifystack-x402-mcp

Official

verifystack_arb_net_profit

Calculates exact arbitrage net profit, break-even spread, and APR after maker/taker fees, slippage, transfer gas, and funding costs.

Instructions

Paid x402 API ($0.005 USDC on Base): Exact arbitrage net profit, break-even spread, and APR calculator accounting for maker/taker fees, slippage, transfer gas, and funding.

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": {
      "notionalUsd": "<notionalUsd>",
      "buyPrice": "<buyPrice>",
      "sellPrice": "<sellPrice>",
      "buyFeeBps": "<buyFeeBps>",
      "sellFeeBps": "<sellFeeBps>"
    },
    "name": "verifystack_arb_net_profit"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyPriceYes
buyFeeBpsYes
holdHoursNo
sellPriceYes
sellFeeBpsYes
notionalUsdYes
slippageBpsNo
fundingRate8hBpsNo
gasAndTransferUsdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the most important non-obvious behavior — this is a paid x402 endpoint costing $0.005 USDC on Base — which is genuinely valuable and not inferable from schema. However, it says nothing about error behavior, precision of returned figures, whether the payment is per-call, or failure modes.

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?

A single dense sentence with no filler, front-loading the paid-API constraint before the functional description. Efficient, though the payment prefix takes the most prominent position rather than the core purpose.

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?

The description names the three outputs (net profit, break-even spread, APR), which partly compensates for the absent output schema, and discloses cost. But for a 9-parameter financial calculator with zero annotation and zero schema coverage, it omits input unit conventions, how slippage is applied per leg, and how holdHours drives the APR.

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 description coverage is 0% across 9 parameters, so the description must compensate. It partially does by naming the accounting factors (maker/taker fees, slippage, transfer gas, funding) that map to buyFeeBps/sellFeeBps, slippageBps, gasAndTransferUsd, and fundingRate8hBps. It adds no meaning for notionalUsd, buyPrice/sellPrice units, or holdHours (only hinted at by 'APR'), leaving required inputs undocumented.

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?

The description uses a specific computational verb set (net profit, break-even spread, APR) over a named resource (arbitrage) and enumerates the cost factors it accounts for. It is clearly distinguishable from siblings like verifystack_live_funding_arb or verifystack_liquidation_sim, though it does not explicitly state the contrast.

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 only implied by the phrase 'arbitrage net profit... calculator' — an agent can infer this is for evaluating a two-venue buy/sell trade. There is no explicit when-to-use, when-not-to-use, or named alternative among the sibling tools, and no mention of prerequisites beyond payment.

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