SAP MCP Server

List SAP Agents

sap_list_agents

Read-onlyIdempotent

Compact SAP agent orientation list. Micro-read when limit <= 20, view is compact, hydrate is false, and includeProtocolIndexes is false; larger or enriched pages are read-premium. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts.

SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

Input Schema

TableJSON Schema

Name	Required	Description
`view`	No	Result shape. Use compact for broad discovery and full for detailed rows. Defaults to compact.
`limit`	No	Maximum rows to return. Defaults to 20; hard-capped at 500.
`query`	No	Optional text search across name, description, agentId, wallet, PDA, x402 endpoint, protocols, capabilities, and active plugins. Example: "XONA" or "creative".
`cursor`	No	Opaque pagination cursor returned as pagination.nextCursor by a previous sap_list_all_agents or sap_discover_agents call.
`offset`	No	Zero-based pagination offset. Defaults to 0. Prefer cursor after the first page when nextCursor is returned.
`wallet`	No	Optional exact owner wallet public key filter. Use this when a wallet is known; it is the most reliable lookup path.
`hydrate`	No	Deprecated compatibility alias. Use view="full" for full rows or view="compact" for directory rows.
`agentPda`	No	Optional exact SAP agent PDA filter.
`protocol`	No	Optional protocol filter matched case-insensitively against agent protocols and protocol-index membership. Example: "jupiter", "creative", "payments".
`capability`	No	Optional single capability ID filter matched case-insensitively. Example: "creative:imageGeneration" or "jupiter:swap".
`capabilities`	No	Optional list of capability IDs. Use capabilityMode="all" when the agent must have every capability.
`capabilityMode`	No	How to match the capability/capabilities filters. Defaults to "any".
`hasX402Endpoint`	No	Optional filter for agents that advertise a paid HTTP/x402 endpoint.
`includeInactive`	No	Include inactive agents. Defaults to false.
`includeProtocolIndexes`	No	Include compact protocol index summaries. Defaults to false for sap_discover_agents and true for sap_list_all_agents.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`content`	Yes	MCP content blocks returned to the caller.
`isError`	No	True when the tool result represents an application-level error.

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already indicate read-only and idempotent, and the description reinforces this with 'Read-only SAP SDK wrapper.' It adds operational context about pricing and routing, which goes beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than necessary, with repetitive guidance about pricing and routing appearing both in the description and schema. It could be more concise without losing essential information.

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

Completeness4/5

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

Given the 15 parameters, no required ones, and an output schema, the description provides sufficient context about usage scenarios (compact vs full) and execution flow. It is fairly complete, though slightly repetitive.

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 100%, so the description adds limited value beyond what the schema provides. The description does set high-level context but does not enhance individual parameter meanings significantly.

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 clearly states it lists SAP agents and distinguishes between compact and full views. However, it does not explicitly differentiate from similar sibling tools like sap_list_all_agents or sap_discover_agents, which reduces clarity.

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?

The description provides some usage context (e.g., inspect chain state before mutations) and conditions for micro-read vs read-premium. But it does not give explicit guidance on when to use this tool over alternatives or when not to use it.

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

All SAP MCP Server tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation4/5

Tools are organized by protocol prefix (e.g., adrena_, jupiter_, sap_) which helps distinguish domains. Within each protocol, tool names clearly indicate actions (e.g., openPosition, getQuote). However, with 360 tools, some cross-protocol overlaps (e.g., multiple swap tools) and many similar fetch tools in the sap_* family require careful reading of descriptions to disambiguate.

Naming Consistency4/5

Each protocol group follows a consistent naming convention (e.g., snake_case for adrena_, camelCase for 3land, sap_ prefix for SAP SDK tools). The mix of conventions across protocols is acceptable, though a uniform style would improve predictability. Minor inconsistency: hyphenated names like metaplex-nft_ vs underscores.

Tool Count2/5

360 tools is far too many for a well-scoped MCP server. This aggregates dozens of protocols and SAP-specific features, making navigation difficult. The server would benefit from being split into focused micro-servers (e.g., SAP identity, Jupiter DEX, NFT tools). The current count overwhelms the coherence of the set.

Completeness4/5

The tool set covers a vast range of Solana ecosystem activities: token operations, swaps, staking, NFT management, bridging, oracle data, identity registration, chat, escrow, subscriptions, and premium streaming. Major lifecycle operations are present, though some niche subdomains may have missing functions (e.g., detailed governance or lending management). Overall, it's comprehensive for the intended scope.

List SAP Agents

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources