Skip to main content
Glama
SAP MultiHopper Mandate Vault MCP Server

SAP MultiHopper Mandate Vault MCP Server

by LBCron

multihopper_quote_fee_split

Computes exact BigInt 0.50% MultiHopper fee and 0.25% integrator revenue share from a raw hop amount, with the share wired to the specified Solana address.

Instructions

Computes exact BigInt 0.50% MultiHopper fee and 0.25% atomic integrator revenue share wired to 32647Bri8KhJQE11x26iF7fpae9nouCJSZ8Y2VPpq5yM.

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": {
      "hopAmountRaw": "<hopAmountRaw>"
    },
    "name": "multihopper_quote_fee_split"
  }
}

Input Schema

NameRequiredDescriptionDefault
hopAmountRawYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description does carry some behavioral load: it discloses exact BigInt integer arithmetic (no floating point), the two fixed rate components, and a hardwired payout address. It does not say whether 'wired to' implies an actual transfer or merely a returned recipient, nor how rounding is handled when the split is not integral, nor whether anything is mutated.

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 front-loaded sentence with no filler; the fixed technical facts (rates, precision, recipient) all earn their place. Slightly dense—the raw address inline makes it harder to scan than a split structure would.

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 one-parameter pure computation with no output schema and no annotations, the description is close but leaves key gaps: the return shape (fee amount, integrator amount, recipient) and the units of hopAmountRaw are unstated. Nothing explains error behavior for invalid or non-numeric strings.

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 0% and the single parameter hopAmountRaw is undocumented, so the description must compensate. It offers only an indirect hint via 'BigInt' that the value is an integer-string in raw base units; it never states the unit, decimals, or valid range.

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 names a specific verb ('Computes') and a specific resource (the MultiHopper fee plus integrator revenue split), with concrete rates of 0.50% and 0.25%. It is clearly distinguishable from the listed siblings (webhook verification, mandate encoding, hierarchy derivation, Solana program verification), though it never explicitly says so.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no routing to an alternative tool. The agent must infer that this is a read-only quote step to be called before a hop transfer.

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