Skip to main content
Glama

basedue__exit

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/exit

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__exit"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / usd
      Removed value: -{
      -  "type": "number"
      -}
  2. Changed2 schema fields changed
    • removedInput schema / properties / size
      Removed value: -{
      -  "type": "number"
      -}
    • addedInput schema / properties / usd
      Added value: +{
      +  "type": "number"
      +}
  3. Changed2 schema fields changed
    • removedInput schema / properties / impact
      Removed value: -{
      -  "type": "string"
      -}
    • changedInput schema / properties / size / type
      Previous value: -"string"New value: +"number"
  4. Changed2 schema fields changed
    • addedInput schema / properties / impact
      Added value: +{
      +  "type": "string"
      +}
    • 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

C2.8/5.0
Behavior3/5

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

With no annotations, the description does add important behavioral context: it discloses the $0.01 x402 payment requirement, the USDC/Base payment rail, and that data comes from public RPC via HTTP GET. However, it does not explicitly confirm read-only behavior, describe error handling, or explain the response shape.

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?

The purpose and endpoint are front-loaded, but the pricing is redundantly restated: '$0.01 per call' appears twice with nearly identical wording. The HTTP endpoint and payment mechanics are useful, but the paragraph could be tightened without losing meaning.

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

Completeness2/5

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

There is no output schema and no annotations, so the description must carry more of the behavioral and parameter burden. It covers payment and transport well, but leaves the token parameter semantics and expected return behavior entirely unspecified, which is a notable gap for a paid due-diligence call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage for the single 'token' parameter is 0%, so the description must compensate and does not. It never explains whether the token is an address, symbol, or other identifier, nor does it mention that the parameter is expected despite being marked optional.

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 states a specific capability set: risk score, flags, liquidity depth, and LP-burn checks for Base tokens. It is clear what the tool does, though the name 'exit' is not explained and the description does not differentiate it from siblings such as basedue__tokenrisk or basedue__due.

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 says the tool works for any Base token, but gives no explicit when-to-use guidance versus alternatives like basedue__tokenrisk or basedue__check. It also does not state that a token must be supplied, despite that being necessary for meaningful use.

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