Skip to main content
Glama

List All SAP Agents

sap_list_all_agents
Read-onlyIdempotent

Paid hosted global SAP agent directory read. Enumerates current on-chain AgentAccount PDAs and supports query, wallet, protocol, capability, x402 endpoint filtering, compact/full views, and cursor pagination. 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
NameRequiredDescriptionDefault
viewNoResult shape. Use compact for broad discovery and full for detailed rows. Defaults to compact.
limitNoMaximum rows to return. Defaults to 100; hard-capped at 500.
queryNoOptional text search across name, description, agentId, wallet, PDA, x402 endpoint, protocols, capabilities, and active plugins. Example: "XONA" or "creative".
cursorNoOpaque pagination cursor returned as pagination.nextCursor by a previous sap_list_all_agents or sap_discover_agents call.
offsetNoZero-based pagination offset. Defaults to 0. Prefer cursor after the first page when nextCursor is returned.
walletNoOptional exact owner wallet public key filter. Use this when a wallet is known; it is the most reliable lookup path.
hydrateNoDeprecated compatibility alias. Use view="full" for full rows or view="compact" for directory rows.
agentPdaNoOptional exact SAP agent PDA filter.
protocolNoOptional protocol filter matched case-insensitively against agent protocols and protocol-index membership. Example: "jupiter", "creative", "payments".
capabilityNoOptional single capability ID filter matched case-insensitively. Example: "creative:imageGeneration" or "jupiter:swap".
capabilitiesNoOptional list of capability IDs. Use capabilityMode="all" when the agent must have every capability.
capabilityModeNoHow to match the capability/capabilities filters. Defaults to "any".
hasX402EndpointNoOptional filter for agents that advertise a paid HTTP/x402 endpoint.
includeInactiveNoInclude inactive agents. Defaults to false.
includeProtocolIndexesNoInclude compact protocol index summaries. Defaults to false for sap_discover_agents and true for sap_list_all_agents.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesMCP content blocks returned to the caller.
isErrorNoTrue when the tool result represents an application-level error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / description
      Added value: +"List All SAP Agents input schema. 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. Use exact field names from this schema; do not guess aliases or include private key material."
    • changedInput schema / properties / capabilities / items / description
      Previous value: -"Capabilities parameter for List All SAP Agents."New value: +"Capabilities array describing agent/tool capabilities. Use stable IDs, protocol labels, and human-readable descriptions; validate category values before writes."
  2. Changed13 schema fields changed
    • addedInput schema / properties / agentPda
      Added value: +{
      +  "description": "Optional exact SAP agent PDA filter.",
      +  "type": "string"
      +}
    • addedInput schema / properties / capabilities
      Added value: +{
      +  "description": "Optional list of capability IDs. Use capabilityMode=\"all\" when the agent must have every capability.",
      +  "items": {
      +    "description": "Capabilities parameter for List All SAP Agents.",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / capability / description
      Previous value: -"Optional capability ID filter such as jupiter:swap."New value: +"Optional single capability ID filter matched case-insensitively. Example: \"creative:imageGeneration\" or \"jupiter:swap\"."
    • addedInput schema / properties / capabilityMode
      Added value: +{
      +  "description": "How to match the capability/capabilities filters. Defaults to \"any\".",
      +  "enum": [
      +    "any",
      +    "all"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Opaque pagination cursor returned as pagination.nextCursor by a previous sap_list_all_agents or sap_discover_agents call.",
      +  "type": "string"
      +}
    • addedInput schema / properties / hasX402Endpoint
      Added value: +{
      +  "description": "Optional filter for agents that advertise a paid HTTP/x402 endpoint.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / hydrate
      Added value: +{
      +  "description": "Deprecated compatibility alias. Use view=\"full\" for full rows or view=\"compact\" for directory rows.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / includeProtocolIndexes / description
      Previous value: -"Include compact protocol index summaries. Defaults to true."New value: +"Include compact protocol index summaries. Defaults to false for sap_discover_agents and true for sap_list_all_agents."
    • changedInput schema / properties / offset / description
      Previous value: -"Zero-based pagination offset. Defaults to 0."New value: +"Zero-based pagination offset. Defaults to 0. Prefer cursor after the first page when nextCursor is returned."
    • changedInput schema / properties / protocol / description
      Previous value: -"Optional protocol filter matched against agent profile protocols and protocol-index membership."New value: +"Optional protocol filter matched case-insensitively against agent protocols and protocol-index membership. Example: \"jupiter\", \"creative\", \"payments\"."
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Optional text search across name, description, agentId, wallet, PDA, x402 endpoint, protocols, capabilities, and active plugins. Example: \"XONA\" or \"creative\".",
      +  "type": "string"
      +}
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "Result shape. Use compact for broad discovery and full for detailed rows. Defaults to compact.",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / wallet
      Added value: +{
      +  "description": "Optional exact owner wallet public key filter. Use this when a wallet is known; it is the most reliable lookup path.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that it is a paid hosted read and gives details about filtering and pagination, which aligns with and extends the annotation information. No contradiction.

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 description is well-structured with a main purpose statement followed by contextual guidance sections. While there is some redundancy (e.g., execution guidance repeated in schema description), each sentence earns its place and the total length is reasonable for the tool's complexity.

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

Completeness5/5

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

Given the tool has 15 parameters, 0 required, 100% schema coverage, an output schema, and clear annotations, the description covers the behavior, filtering, pagination, and execution context thoroughly. No gaps are apparent.

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 input schema already documents all 15 parameters with descriptions. The description mentions key filtering options (query, wallet, protocol, etc.) but does not add new semantic meaning beyond what is in the schema. Baseline 3 is appropriate.

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 agent PDAs with filtering and pagination, specifying it's a read operation. It does not explicitly differentiate from sibling 'sap_discover_agents', but the verb 'list all' implies a broader scope, and the filtering details make the purpose specific.

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

Usage Guidelines4/5

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

The description provides explicit guidance on intent (read/discovery workflow), pricing (paid read-premium), and routing instructions (estimate first, use payment tool if needed). It does not state when to avoid this tool versus alternatives, but the context is clear and actionable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.