Skip to main content
Glama

BRAINIAC Token Security & Risk Intelligence

Liquidity risk assessment

token-security_liquidity-risk-assessment
Read-onlyIdempotent

Assess Base pool liquidity reported by the public DEX Screener API, including concentration across returned pools. LP lock is not verified. Price $0.04 USDC. POST /api/v1/token-security/liquidity-risk-assessment. 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_liquidity-risk-assessment"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYestokenAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
poolsNopools. Array.
statusNostatus. String.
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.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/openWorld/idempotent annotations, the description discloses important operational behavior: the DEX Screener data source, the LP-lock verification gap, the $0.04 USDC price, the POST endpoint, and critically that an unpaid x402 call returns payment terms and does not execute. This is material context an agent needs before calling it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the core assessment function, then adds high-value caveats about LP lock and payment behavior. Every sentence carries relevant information for invocation or interpretation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the single-parameter schema, existing output schema, and rich annotations, the description covers the essential purpose, data source, limitation, chain context, and x402 payment behavior. Nothing critical for an agent to call the tool correctly is missing.

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?

There is only one parameter, and the schema already documents tokenAddress with 100% coverage including its required status and address pattern. The description adds no additional meaning about the parameter, which is acceptable given the complete schema coverage.

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 clearly states a specific verb and resource: assess Base pool liquidity reported by the public DEX Screener API, including concentration across returned pools. It does not explicitly contrast itself with sibling risk tools, but the scope is specific enough that an agent can distinguish it from honeypot, ownership, and deployer checks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool assesses and notes that LP lock is not verified, but it does not say when to use this assessment versus alternatives such as the risk verdict or other token-security checks. Usage is only inferable from the purpose statement.

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