SAP MCP Server

Spl-token Get Token Accounts

spl-token_getTokenAccounts

Read-onlyIdempotent

List all SPL token accounts for a wallet with balances and metadata. SAP MCP context: Protocol spl-token; operation class write. Use for SPL token deploy, mint, transfer, burn, freeze, thaw, and authority management. Confirm mint, decimals, authority, recipient, and amount before writes. Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle. Parameter aliases accepted by SAP MCP for agent ergonomics: owner -> wallet, address -> wallet, pubkey -> wallet. Prefer the canonical schema names in new calls.

SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. 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	Default
No arguments

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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 24, 2026

addedInput schema / description

Added value: +"Spl-token Get Token Accounts input schema. Intent: read/discovery workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. 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."

Changed4 schema fields changedJul 17, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / showZeroBalance

Removed value: -{
-  "description": "Include zero-balance accounts",
-  "type": "boolean"
-}

removedInput schema / properties / wallet

Removed value: -{
-  "description": "Wallet to query all token accounts for",
-  "type": "string"
-}

removedInput schema / required
```
Removed value: -[
-  "wallet"
-]
```

First observedJul 13, 2026

TDQS

C2.1/5.0

Behavior2/5

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

The description adds information like 'Intent: read/discovery workflow' and 'Pricing: free' beyond annotations, but it also contains a direct contradiction by stating 'operation class write' while annotations set readOnlyHint=true. This inconsistency reduces transparency.

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

Conciseness2/5

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

The description is verbose, containing repetitive SAP MCP boilerplate and two separate sections. The critical information is diluted by extraneous context and contradictory statements, making it less concise than necessary.

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?

Given the tool has no parameters but an output schema, the description should clarify output structure and differentiate from spl-token_getBalance. It mentions 'balances and metadata' but not specifics, and the contradictory write-operation guidance leaves the agent incompletely informed.

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?

The input schema has 0 parameters, so there is nothing to explain. However, the description mentions parameter aliases like 'owner -> wallet' which do not exist in the schema, creating confusion rather than adding value.

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 states 'List all SPL token accounts for a wallet with balances and metadata,' which is a clear purpose. However, it is undermined by contradictory statements like 'operation class write' and 'Use for SPL token deploy, mint, transfer...' that suggest write capabilities, confusing the tool's actual read-only nature.

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?

The description provides vague guidance such as 'Use token tools alongside SAP payments and settlement tools only when token operations are part of the agent service lifecycle.' It fails to explicitly differentiate from sibling tools like spl-token_getBalance and incorrectly suggests using this tool for write operations, misleading the agent.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.