Skip to main content
Glama

BRAINIAC Token Security & Risk Intelligence

Two-source token price check

token-security_price-two-source
Read-onlyIdempotent

Compare an on-pool DEX Screener USD price (deepest Base pool) with DeFiLlama coins API for base:. The two feeds are independent aggregators; agree=pass can still reflect overlapping underlying pools when both quote the same liquidity. agree is pass, fail, or not_checked; a single source never yields agree=pass. Price $0.03 USDC. POST /api/v1/token-security/price-two-source. 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_price-two-source"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYestokenAddress, string. Required.
tolerancePctNotolerancePct, number, from any to 50. Required.

Output Schema

NameRequiredDescriptionDefault
poolNopool. Object.
agreeNoagree. String.
pricesNoprices. Array.
statusNostatus. String.
sourcesNosources. Array.
result_idNoresult_id. String.
limitationsNolimitations. Array.
received_atNoreceived_at. String.
retrievedAtNoretrievedAt. String.
tokenAddressNotokenAddress. String.
deviation_pctNodeviation_pct. Number.
missing_itemsNomissing_items. Array.
tolerance_pctNotolerance_pct. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations by disclosing the possible agree values (pass, fail, not_checked), the epistemic caveat that agreement can still stem from overlapping underlying pools, the $0.03 USDC cost, and that an unpaid call returns x402 payment terms without executing. These are exactly the behavioral facts an agent needs before invoking a paid external call.

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 comparison, the agree semantics, the caveat, the price, and the endpoint are packed into a few dense sentences with the core purpose front-loaded. 'Price $0.03 USDC.' is terse to the point of being slightly cryptic, but no sentence is wasted.

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?

For a two-parameter, read-only, paid external call with an output schema already available, the description covers what is compared, how results are interpreted, cost, and payment failure behavior. Nothing an agent needs in order to call it correctly or interpret a refusal 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?

Schema coverage is 100%, so both tokenAddress and tolerancePct are already documented, and the description only clarifies that the token is queried as base:<token> on the DeFiLlama side. It adds nothing about tolerancePct semantics or what the tolerance controls in the pass/fail decision, so the 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: compare a DEX Screener on-pool USD price against the DeFiLlama coins API for base:<token>, naming both feeds and the deepest Base pool. The purpose is unambiguous and distinct in practice from the risk-oriented siblings, though the description never explicitly contrasts itself with them.

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 rather than stated: the 'two-source' framing plus 'a single source never yields agree=pass' tells an agent this is for independent price corroboration, but there is no explicit when-to-use or when-to-prefer-an-alternative guidance. Payment handling is described, which helps the agent decide whether to call, but that is operational rather than selection guidance.

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