Skip to main content
Glama

basedue__due

Due-diligence check for one Base token: verdict, risk score, flags and liquidity summary, from public Base RPC. Pass the token contract address as the 'token' query parameter. Price $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/due

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

Input Schema

NameRequiredDescriptionDefault
tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations present the description carries the full burden, and it does disclose non-obvious behavior: execution reads public Base RPC, the call costs $0.01 USDC on Base (eip155:8453) settled via x402 in params._meta['x402/payment'], and it exposes the concrete HTTP endpoint. What it omits are failure modes and whether the token address must be a contract rather than an EOA, which matters for a risk-check tool.

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 payment terms are front-loaded and the endpoint is useful. However, the pricing is stated twice in near-identical wording ('Price $0.01 per call' then 'Price: $0.01 per call in USDC on Base'), which is redundant filler in an otherwise short description.

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?

Given a single-parameter tool with no output schema, the description covers both what goes in and what comes back, and it explains the payment prerequisite an agent would otherwise be blocked by. The remaining gap is behavioral edge cases around invalid or non-contract token addresses.

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 0% for the single 'token' parameter, but the description separately says to pass the token contract address as the 'token' query parameter, which fully supplies the meaning the schema lacks. It stops short of adding format details such as checksum or chain-prefix expectations, so it is adequate rather than rich.

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 ('Due-diligence check for one Base token') and enumerates the return payload (verdict, risk score, flags, liquidity summary) plus the data source (public Base RPC). It is clear in isolation but never contrasts itself with nearby siblings such as basedue__tokenrisk or basedue__check, so an agent must guess which due-diligence variant to call.

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 phrase 'Due-diligence check for one Base token', which does establish the single-token scope, and it adds an instruction to pass the token contract address as the 'token' query parameter. There is no explicit when-to-use versus when-not guidance and no named alternative among the many risk-oriented siblings, leaving routing to inference.

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