Skip to main content
Glama

BRAINIAC Token Security & Risk Intelligence

Token manipulation signals

token-security_manipulation-signals
Read-onlyIdempotent

Report buy, sell, price-change, and volume signals from public DEX Screener data for the largest Base pool. These are feed observations, not proof of manipulation. Price $0.04 USDC. POST /api/v1/token-security/manipulation-signals. 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_manipulation-signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYestokenAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
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 annotations (which only say read-only, idempotent, open-world, non-destructive), the description discloses the data source, the pool scope, the $0.04 USDC cost, and crucially the x402 payment flow — an unpaid call returns payment terms and does not execute. That payment-gating behavior is exactly the kind of operational trait an agent cannot get from structured fields.

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?

Five short sentences, front-loaded with the purpose and caveated immediately, then price and payment behavior. Every sentence is functional; the raw endpoint path is the only mildly redundant element.

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 only one parameter, an output schema already covering return values, and annotations covering the safety profile, the description supplies the missing pieces: cost, payment behavior, data provenance, and interpretive limits. Minor gaps remain, such as what happens when the token has no qualifying Base pool.

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 description coverage is 100% and the single tokenAddress parameter already carries a regex pattern and required flag, so the schema does the work. The description adds no syntax or format detail about tokenAddress, leaving this at the baseline.

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 names a specific verb and resource set ('Report buy, sell, price-change, and volume signals') plus the data source (public DEX Screener) and scope ('largest Base pool'). It is clearly distinguishable from siblings like honeypot-risk-check or price-two-source, though it 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 tool is framed as feed observation for the largest Base pool, and the caveat 'not proof of manipulation' tells the agent how to interpret results. However, there is no explicit when-to-use/when-not guidance and no named alternative for agents that need verified or two-source pricing.

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