Skip to main content
Glama

BRAINIAC Wallet Intelligence

Generate security report

wallet-intelligence_security-report
Read-onlyIdempotent

Generate a combined security report using GoPlus Labs address security and approval checks on Base Mainnet. Price $0.10 USDC. POST /api/v1/wallet-intelligence/security/risk-report. 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-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletAddressYeswalletAddress, string. Required.
includeAddressCheckNoincludeAddressCheck, boolean. Required.
includeApprovalCheckNoincludeApprovalCheck, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
sourcesNosources. Array.
findingsNofindings. 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, openWorld, and non-destructive, so the bar is lower. The description still adds real value by disclosing the $0.10 USDC cost, the x402 payment flow, and the important failure mode that an unpaid call returns payment terms and does not execute — information unavailable anywhere else.

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 sentences, front-loaded with the purpose, then cost and payment behavior. The raw endpoint path is arguably low-value for an agent, but everything else earns its place and nothing is buried.

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 values need not be explained, and annotations cover the safety profile. The description closes the remaining gap — cost and the unpaid-call behavior — though it says nothing about latency, caching of paid results, or what the combined report distinguishes from the sibling endpoints.

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 description coverage is 100%, so all three parameters (walletAddress, includeAddressCheck, includeApprovalCheck) are documented in the schema. The description adds nothing about what the two boolean toggles change in the report, 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?

States a specific verb and resource: 'Generate a combined security report' scoped to 'GoPlus Labs address security and approval checks on Base Mainnet'. The word 'combined' implicitly distinguishes it from the granular security-address and security-approvals siblings, though neither is named explicitly.

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?

The description implies this is the aggregate option ('combined ... address security and approval checks'), but it never states when to prefer it over the separate address or approvals tools, nor any prerequisite beyond payment. Usage must be inferred from the scope wording.

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