Skip to main content
Glama
SAP MultiHopper Mandate Vault MCP Server

SAP MultiHopper Mandate Vault MCP Server

by LBCron

sap_derive_hierarchy

Derives deterministic OOBE SAP v2, MultiHopper Core/Orchestrator, and SAP Mandate Vault PDAs from owner, agent wallet, vault ID, and route inputs.

Instructions

Derives deterministic OOBE SAP v2, MultiHopper Core/Orchestrator, and SAP Mandate Vault PDAs.

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": {
      "owner": "<owner>",
      "agentWallet": "<agentWallet>",
      "vaultId": "<vaultId>",
      "routeHex": "<routeHex>"
    },
    "name": "sap_derive_hierarchy"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
ownerYes
vaultIdYes
routeHexYes
agentWalletYes

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?

No annotations are supplied, so the description carries the full behavioral burden. It discloses only that the derivation is deterministic; it does not state whether the call is read-only, whether it touches the network, what happens on invalid inputs, or what it returns.

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?

The definition is a single front-loaded sentence with no filler. Its density of undefined acronyms slightly reduces clarity, but structurally it is efficient.

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

Completeness1/5

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

For a tool with five parameters, four required, zero parameter descriptions, no annotations, and no output schema, one sentence is not enough. The definition leaves the agent without the information needed to invoke it confidently.

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

Parameters1/5

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

All five parameters (owner, agentWallet, vaultId, routeHex, mint) have 0% schema description coverage and the description mentions none of them. The agent receives no meaning beyond the parameter names and JSON types.

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 verb ('Derives') and names the exact PDA families produced (OOBE SAP v2, MultiHopper Core/Orchestrator, SAP Mandate Vault). That is enough to distinguish it from the verification and encoding siblings, though the acronym-heavy phrasing is less accessible than a plain statement of the operation.

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 to call this tool versus the sibling tools, nor any prerequisites or exclusions. The agent must infer its role entirely from the verb and resource.

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