Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

Read a user's SOMA Coins wallet (read-only, token required)

get_wallet
Read-only

READ-ONLY wallet summary for a SOMA app user: their SOMA Coins balance plus a summary of coins expiring within the next 30 days. Requires a wallet token that only the human can generate inside the SOMA mobile app (Wallet tab → 'Share balance with your AI') — ask them for it; tokens expire after ~10 minutes. This tool can never claim, redeem, spend, or move coins (there are deliberately no claim/redeem tools over MCP). Returns { error: 'invalid_or_expired_token' } for a bad or stale token — ask the user to generate a fresh one in the app.

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": {
      "wallet_token": "<wallet_token>"
    },
    "name": "get_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
wallet_tokenYesThe short-lived wallet token the user generated in the SOMA app (Wallet tab → 'Share balance with your AI') and pasted to you

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint by disclosing token provenance and human-only generation, a ~10-minute expiry, and the exact failure surface ({ error: 'invalid_or_expired_token' }) with the prescribed recovery step. It also rules out side effects (cannot claim, redeem, spend, or move coins), which is the key behavioral risk for a coins-related tool.

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?

Front-loads the read-only scope and payload before the token mechanics, and every sentence carries operational value. It is denser than needed for one parameter, with nesting of the token path and error recovery into single sentences, but nothing is filler.

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?

Despite having no output schema, the description tells the agent what a successful response contains (balance plus expiring-coin summary) and what an error response looks like, plus the recovery loop. For a single-parameter read tool this leaves no operational gap.

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

Parameters4/5

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

With one parameter at 100% schema coverage the baseline is 3, but the description adds meaning the schema does not carry: only the human can mint the token, it expires after roughly 10 minutes, and a stale token surfaces as a specific error. It restates the Wallet-tab generation path already present in the schema, which caps it below a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource+scope: 'READ-ONLY wallet summary for a SOMA app user' and enumerates exactly what is returned (balance + coins expiring in 30 days). It also explicitly disclaims the adjacent write capabilities (claim/redeem/spend/move), so an agent can distinguish this from any write path without inspecting schemas.

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

Usage Guidelines5/5

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

States the precondition (a wallet token only the human can generate, in the SOMA app Wallet tab), instructs the agent to ask the user for it, and explains the token lifetime (~10 minutes). It also names what does not exist as a tool ('deliberately no claim/redeem tools over MCP'), so the agent will not go looking for an alternative.

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.

Resources