Skip to main content
Glama

BRAINIAC Token Due Diligence

Inspect DEX liquidity

token-due-diligence_liquidity
Read-onlyIdempotent

Inspect supported DEX liquidity pools on Base Mainnet using official Uniswap V2 and V3 factories. Price $0.05 USDC. POST /api/v1/token-due-diligence/liquidity. 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_liquidity"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYestokenAddress, string. Required.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description is not required to restate it. It instead adds behavior an agent could not infer elsewhere: a $0.05 USDC price, the POST endpoint, and the crucial detail that an unpaid call returns x402 payment terms without executing. It stops short of saying anything about result shape or pool coverage limits, but the output schema carries the return contract.

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?

Three compact sentences: purpose first, then cost/endpoint, then the payment gate. Every sentence carries information an agent needs (scope, price, failure mode) and there is no filler.

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 tool with full schema coverage, an output schema, and complete annotations, the definition covers what is needed to call it correctly, including the paid-call behavior. The remaining gap is minor: it does not hint at which pools or how many results come back, though the output schema covers that.

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 a single parameter, tokenAddress, and schema description coverage is 100% with a regex pattern constraining format. The description adds no further meaning about this parameter, so the baseline 3 applies when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Inspect supported DEX liquidity pools'), plus the chain (Base Mainnet) and the data source (official Uniswap V2 and V3 factories). That is enough for an agent to distinguish it from siblings like holders, honeypot, permissions, and security-report without opening a schema.

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 the scope: the tool returns liquidity data for a single token on Base Mainnet. There is no explicit statement of when to pick this over token-due-diligence_analyze or security-report, and no conditions for exclusion are given.

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