Skip to main content
Glama

basedue__price

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

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

Input Schema

NameRequiredDescriptionDefault
tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description does useful behavioral work by disclosing that this is a paid call ($0.01 USDC on eip155:8453 via x402 in params._meta['x402/payment']), the data source (public RPC), and the HTTP endpoint. However, it omits what the call returns, whether the token parameter is optional and what happens if it is absent, and any rate-limit or failure behavior — significant gaps for an unannotated 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 core capability is front-loaded in the first sentence, which is good, but the '$0.01 per call' cost is stated twice in back-to-back sentences and the trailing raw HTTP endpoint adds little for an MCP consumer. Roughly a third of the text is redundant.

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?

For an unannotated, no-output-schema tool with an undocumented optional parameter, the description should cover return shape or the omitted-parameter behavior and its relationship to sibling risk tools; it covers none of these. The payment details are the only completeness win.

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 coverage is 0% and one parameter (token, not required) is completely undocumented. The description never says whether token is a contract address, a symbol, or what default is used when it is omitted — exactly the information the schema fails to provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a reasonably specific purpose — risk score, flags, liquidity depth and LP-burn checks for a Base token via public RPC — but it does not match the tool name 'price' (no pricing/quote behavior is described), and the siblings basedue__tokenrisk, basedue__due and basedue__check look like near-identical risk surfaces with no differentiation. An agent can tell it performs token due diligence but cannot tell what makes it distinct from those siblings.

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?

There is no when-to-use guidance, no exclusions, and no named alternative among the many risk-related siblings (due, tokenrisk, check, compare, report). The only conditional information is the price/payment mechanic, which is a precondition 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