Skip to main content
Glama

BRAINIAC Wallet Intelligence

Check address security

wallet-intelligence_security-address
Read-onlyIdempotent

Check wallet address for malicious activity indicators using GoPlus Labs threat intelligence on Base Mainnet. Price $0.05 USDC. POST /api/v1/wallet-intelligence/security/address. 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-address"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletAddressYeswalletAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
sourcesNosources. Array.
securityNosecurity. 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 cover readOnly, idempotent, openWorld and non-destructive, so the safety profile is handled structurally. The description adds genuinely new behavior: the $0.05 USDC price, the x402 payment mechanism, and critically that an unpaid call returns payment terms and does not execute — a failure mode an agent must know about.

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 the purpose and followed by cost and the payment caveat. The raw endpoint path (POST /api/v1/wallet-intelligence/security/address) is marginally useful but borders on noise for an agent that only needs to call the tool.

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?

With annotations, a full output schema, and one well-documented parameter, the description only needs to cover cost and payment behavior — which it does precisely. Minor omissions like latency or rate limits are acceptable given the structured data already supplied.

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% with a single required 'walletAddress' that already specifies the 0x-prefixed 40-hex pattern in the schema. The description adds no meaning beyond that (no notes on chain-specific formatting or checksum expectations), so the baseline of 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 and resource ('Check wallet address for malicious activity indicators') plus the data source (GoPlus Labs) and network (Base Mainnet), which is more than the title alone conveys. It does not explicitly distinguish itself from siblings like wallet-intelligence_security-approvals or wallet-intelligence_security-report, so an agent must infer the boundary from names.

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 only implied: an agent can infer this is the tool for screening a single address for risk. There is no explicit statement of when to prefer it over security-report or security-approvals, and no prerequisites or exclusions are named.

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