Skip to main content
Glama
Sign In

SealGuard

by io.github.2cstudiodev-web
OverviewDiscussionsAdmin

List open token approvals

list_token_approvals
Read-only

Lists every token approval (delegate) on a Solana wallet: which address can still move which token, and how much. Also lists Token-2022 permanent delegates, which holders can't revoke. Read-only; returns a link where the owner can revoke approvals for free.

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": {
      "address": "<address>"
    },
    "name": "list_token_approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe Solana wallet address (base58 public key) to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is in scope details: it covers Token-2022 permanent delegates, which are flagged as non-revocable by holders — an important behavioral nuance that affects what the agent can do with the result. It also discloses that a revocation link is returned despite there being no output schema. Pagination or rate-limit behavior is not mentioned.

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?

Two dense sentences, front-loaded with what is listed, followed by the revoke-link payoff. The only near-waste is 'Read-only', which restates the readOnlyHint annotation rather than adding new 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?

For a simple one-parameter read tool with annotations and no output schema, the description covers what is enumerated, the non-revocable edge case, and the returned link. Minor gaps remain around whether native SOL or only SPL/Token-2022 approvals are included and whether results are paginated.

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?

With a single required parameter and 100% schema description coverage, the schema already documents 'address' as a base58 Solana public key. The description only implies the address identifies the wallet being checked, adding no format or validation detail beyond the schema, so baseline 3 applies.

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 uses a specific verb and resource ('Lists every token approval (delegate) on a Solana wallet') and clarifies the payload with 'which address can still move which token, and how much'. It does not explicitly contrast itself with siblings like list_empty_token_accounts or scan_wallet, but the subject matter is distinct enough that an agent can tell them apart.

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?

Usage is implied rather than stated: checking a wallet for outstanding delegations, with the added hook of a free revocation link. There is no explicit when-not guidance and no named alternative for related tasks such as scanning a wallet's overall exposure.

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

All SealGuard toolsInspect
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.

Resources