Skip to main content
Glama

BRAINIAC Token Due Diligence

Inspect contract permissions

token-due-diligence_permissions
Read-onlyIdempotent

Inspect contract ownership and privileged controls on Base Mainnet including owner, admin, and upgradeability. Price $0.03 USDC. POST /api/v1/token-due-diligence/permissions. 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-due-diligence_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYestokenAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
chainIdNochainId. Number.
sourcesNosources. Array.
result_idNoresult_id. String.
limitationsNolimitations. Array.
permissionsNopermissions. Object.
received_atNoreceived_at. String.
retrievedAtNoretrievedAt. String.
tokenAddressNotokenAddress. String.
missing_itemsNomissing_items. Array.

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 read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond annotations by stating the $0.03 USDC price and that an unpaid call returns x402 payment terms and does not execute, which directly affects invocation behavior.

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 purpose is front-loaded in the first sentence, followed by payment details and the endpoint. The endpoint line is somewhat operational rather than semantic, but the description remains compact and easy to scan.

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 single-parameter, read-only inspection tool with an output schema, the description gives enough scope, chain, and payment context to invoke correctly. Explicit sibling routing is missing, but return values are covered by the output schema.

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%, and the single tokenAddress parameter is fully defined by the schema with its required status and address pattern. The description adds no additional parameter meaning, so the baseline of 3 is appropriate.

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 states a specific verb and resource: inspect contract ownership and privileged controls on Base Mainnet, including owner, admin, and upgradeability. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as security-report or honeypot.

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 due-diligence framing and the focus on ownership and privileged controls, but the description gives no explicit when-to-use guidance, exclusions, or named alternatives among the sibling tools.

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