Skip to main content
Glama
SAP MultiHopper Mandate Vault MCP Server

SAP MultiHopper Mandate Vault MCP Server

by LBCron

mandate_evaluate_and_encode

Evaluates Solana mandate-vault policy checks (≥20 USDC gate, rolling 24h cap, anti-wash rules) and encodes the Anchor authorize_multihopper_route instruction for MultiHopper routing.

Instructions

Evaluates Steve Capital >=20 USDC gate, rolling 24h cap, anti-wash rules, and encodes the Anchor authorize_multihopper_route instruction.

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": {
      "agentWallet": "<agentWallet>",
      "ownerWallet": "<ownerWallet>",
      "fundedUsdcMicro": "<fundedUsdcMicro>",
      "usdcEquivMicro": "<usdcEquivMicro>",
      "hopAmountRaw": "<hopAmountRaw>",
      "recipients": "<recipients>"
    },
    "name": "mandate_evaluate_and_encode"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipientsYes
agentWalletYes
ownerWalletYes
hopAmountRawYes
usdcEquivMicroYes
fundedUsdcMicroYes
intermediateHopsNo
dailyCapUsdcMicroNo
maxPerRouteUsdcMicroNo
windowSpentUsdcMicroNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden for a 10-parameter tool. It does not state whether the 20 USDC gate failure throws an error, returns a boolean, or silently skips encoding, nor whether anything is submitted on-chain versus merely serialized, nor whether evaluation is deterministic or requires network access.

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, and the evaluated rules are front-loaded ahead of the encoding action. It is compact but packs multiple clause-level concepts with no separating structure.

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

Completeness2/5

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

For a high-complexity, 10-parameter tool with no output schema and no annotations, the definition is far too thin. An agent lacks the failure semantics, return shape, and parameter meaning needed to invoke it correctly, so substantial gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters, and the description explains none of them. The '20 USDC gate' loosely maps to fundedUsdcMicro, but critical distinctions such as fundedUsdcMicro vs usdcEquivMicro vs windowSpentUsdcMicro, and the meaning of hopAmountRaw string units or weightBps, are left entirely undocumented.

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

Purpose3/5

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

The description names two concrete actions (evaluating a set of gate rules and encoding an 'authorize_multihopper_route' instruction), which is more than a restatement of the name. However, it leans on unexplained domain jargon ('Steve Capital', 'anti-wash rules') and gives no signal about how it differs from siblings like multihopper_quote_fee_split, so an agent cannot confidently distinguish its role.

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 indication of when this tool should be chosen over the fee-split quote or webhook verification siblings. The phrase 'evaluates ... gate' hints at a pre-flight check role, but the agent must infer that entirely.

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