Skip to main content
Glama
SAP MultiHopper Mandate Vault MCP Server

SAP MultiHopper Mandate Vault MCP Server

by LBCron

solana_verify_mainnet_programs

Verifies whether OOBE SAP v2 and MultiHopper programs are executable on Solana Mainnet-Beta, confirming live deployment status before use.

Instructions

Verifies live Solana Mainnet-Beta executable status of OOBE SAP v2 and MultiHopper programs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "solana_verify_mainnet_programs"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpcUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that this performs a live network check against Mainnet-Beta (not a cached or local inspection), but says nothing about failure semantics, whether it is strictly read-only, latency/rate-limit characteristics, or what the response contains despite there being no output schema.

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 or redundancy. It is efficient, though the terseness contributes to the gaps in usage and parameter guidance.

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 tool with an undocumented optional parameter, no annotations, and no output schema, the description should explain the default endpoint and what a verification result looks like. It identifies the subject of verification but leaves the agent unable to predict the call's behavior or return value.

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% for the single optional 'rpcUrl' parameter, and the description never mentions it. It does not say what endpoint is used when rpcUrl is omitted, whether a custom URL is required for private clusters, or what format is expected, so it fails to compensate for the schema gap.

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?

States a specific verb ('Verifies') and a specific resource ('live Solana Mainnet-Beta executable status of OOBE SAP v2 and MultiHopper programs'), naming the exact programs and network. That is enough to tell it apart from the listed siblings (webhook verification, fee-split quoting, hierarchy derivation), though it never explicitly contrasts with them.

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 guidance, no stated prerequisites (e.g., that a reachable RPC endpoint is required), and no indication of what to do if verification fails. The use case can be inferred from the verb, but nothing is explicitly framed as a selection criterion.

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