Skip to main content
Glama

basedue__report

Base token due diligence: risk score, flags, liquidity depth and LP-burn checks for any Base token, from public RPC. $0.01 per call. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/basedue/report

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "basedue__report"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed1 schema field changed
    • removedInput schema / properties / size
      Removed value: -{
      -  "type": "string"
      -}
  4. Changed1 schema field changed
    • addedInput schema / properties / size
      Added value: +{
      +  "type": "string"
      +}
  5. Changed2 schema fields changed
    • addedInput schema / properties / token
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / tokens
      Removed value: -{
      -  "type": "string"
      -}
  6. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied the description carries the full burden, and it does disclose the material behavior: pay-per-call cost, the exact payment rail (x402 USDC on eip155:8453, passed in params._meta["x402/payment"]), a read-only GET transport, and the upstream data source. It omits rate limits, failure/timeout behavior when RPC data is thin, and what a partial-coverage token returns.

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

Conciseness3/5

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

Front-loaded and mostly tight, but the price is stated twice ("$0.01 per call" then again "Price: $0.01 per call in USDC..."), costing a sentence of redundancy. The payment and HTTP details are genuinely useful and well placed at the end.

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 paid endpoint with no output schema, the description supplies what an agent needs to invoke and pay for it. The remaining gap is the token identifier format, which is the one thing that could cause a malformed call.

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?

The single parameter has 0% schema description coverage, so the description must compensate; "for any Base token" implies the value identifies a Base-chain token but does not state whether it takes a contract address, a symbol, or either. That ambiguity is the main practical risk when invoking this tool.

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?

Names a specific verb+resource ("Base token due diligence") and enumerates what the report contains: risk score, flags, liquidity depth, LP-burn checks, plus the data source (public RPC). It does not distinguish itself from near-neighbours such as basedue__due, basedue__tokenrisk or basedue__check, which is the only thing keeping it off a 5.

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?

Gives no when-to-use or when-not-to-use guidance and never names an alternative for a lighter or differently-scoped check. The agent must infer from the name alone that this is the full due-diligence call versus the cheaper single-signal siblings.

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