Skip to main content
Glama

BRAINIAC Token Security & Risk Intelligence

Ownership risk check

token-security_ownership-risk-check
Read-onlyIdempotent

Read owner(), EIP-1967 proxy slots, and bytecode selectors for mint, pause, and blacklist privileges on Base. Selector presence is not proof the owner can call them. Price $0.04 USDC. POST /api/v1/token-security/ownership-risk-check. 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": {
      "tokenAddress": "<tokenAddress>"
    },
    "name": "token-security_ownership-risk-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYestokenAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
chainIdNochainId. Number.
sourcesNosources. Array.
findingsNofindings. Array.
result_idNoresult_id. String.
assessmentNoassessment. String.
limitationsNolimitations. Array.
received_atNoreceived_at. String.
retrievedAtNoretrievedAt. String.
tokenAddressNotokenAddress. String.
missing_itemsNomissing_items. Array.
approvesInteractionNoapprovesInteraction. Boolean.

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 establish read-only, idempotent, non-destructive, open-world behavior, and the description adds genuinely non-structural facts: the $0.04 USDC price, the x402 flow, and that an unpaid call returns payment terms without executing. It also pre-empts a likely misinterpretation by stating selector presence is not proof the owner can call them, though it does not flag rate limits or behavior on unsupported chains.

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?

The what/where leads, followed by the interpretive caveat, then pricing, endpoint, and payment-failure behavior — a sensible front-loaded order with no filler. The endpoint path and price are somewhat operational noise for an agent but each still carries decision-relevant 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?

With one simple required param, an output schema, and full annotations, the definition covers what is read, which chain, cost, and what happens on an unpaid call. The main residual gap is the absence of guidance on how this partial ownership signal should be combined with the other risk checks.

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?

Only one parameter (tokenAddress) exists and schema description coverage is 100%, so the schema already carries its meaning. The description adds no format or validation detail beyond implying the token is on Base, which is a useful but marginal addition.

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?

"Read owner(), EIP-1967 proxy slots, and bytecode selectors for mint, pause, and blacklist privileges" names a concrete verb and the exact on-chain evidence inspected, which is clearly distinct from the honeypot, liquidity, and sell-simulation siblings. It stops short of naming which sibling to pick instead when ownership risk is only one part of a broader review.

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 by scope: an agent can infer this is for checking privileged-role exposure on a Base token. There is no explicit when-to-use, when-not-to-use, or routing to token-security_risk-verdict or token-security_due-diligence-report when a partial signal is not enough.

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