Skip to main content
Glama

BRAINIAC Wallet Intelligence

Check approval security

wallet-intelligence_security-approvals
Read-onlyIdempotent

Check wallet address for risky token approvals and permissions using GoPlus Labs risk analysis on Base Mainnet. Price $0.05 USDC. POST /api/v1/wallet-intelligence/security/approvals. An unpaid call returns the x402 payment terms and does not run.

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": {
      "walletAddress": "<walletAddress>"
    },
    "name": "wallet-intelligence_security-approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletAddressYeswalletAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
sourcesNosources. Array.
approvalsNoapprovals. Object.
result_idNoresult_id. String.
limitationsNolimitations. Array.
received_atNoreceived_at. String.
retrievedAtNoretrievedAt. String.
missing_itemsNomissing_items. Array.
walletAddressNowalletAddress. String.

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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: a $0.05 USDC price, the x402 payment flow, and critically that an unpaid call returns payment terms without executing — that last point materially changes how an agent should interpret a response.

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?

Three short sentences, front-loaded with purpose, then cost, then endpoint, then the payment caveat. No padding; the raw endpoint path is marginally redundant with the tool name but harmless.

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?

An output schema exists, so return structure needn't be explained, and the payment/execution caveat covers the main failure mode an agent would hit. The remaining gap is that 'risky' is never characterized and no coverage limits beyond Base Mainnet are stated.

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 parameter at 100% schema description coverage, the schema (including the 0x address pattern) already carries the semantics. The description adds nothing about the walletAddress beyond what the schema states, so the 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?

States a specific verb (check) and resource (risky token approvals and permissions for a wallet address), plus the data provider (GoPlus Labs) and network (Base Mainnet). That specificity distinguishes it from a generic address-reputation sibling, but it never explicitly contrasts itself with wallet-intelligence_security-address or security-report, leaving the boundary to inference.

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 by the resource description: an agent can infer this is the tool for approval/permission exposure on a wallet. There is no explicit when-to-use, when-not-to-use, or alternative-routing guidance relative to the security siblings.

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