Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

basedue__check

Quick pass/fail safety check for a Base token. 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/check

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

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 / url
      Removed value: -{
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • removedInput schema / properties / token
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / token
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / url
      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 / url
      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 / url
      Removed value: -{
-  "type": "string"
-}
  6. Changed2 schema fields changed
    • removedInput schema / properties / token
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
  7. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful behavior: the $0.01 USDC cost on Base, the x402 payment location in params._meta, and the HTTP endpoint. However it never says what pass/fail means, what dimensions are checked, or how a failed payment or unknown token is reported.

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?

Two compact sentences, front-loaded with purpose followed by the payment and transport mechanics. Nothing is padded, although the raw endpoint URL is arguably operational detail rather than decision-relevant for the agent.

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

Completeness3/5

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

For a one-parameter check with no output schema and no annotations, the description covers cost and access mechanics but not the token identifier format or what the pass/fail verdict contains. Those omissions are material for a paid screening 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 coverage is 0% for the single 'token' parameter, so the description must compensate — and it only says 'Base token', leaving the format ambiguous (contract address vs symbol vs name). That ambiguity is the most likely cause of a failed call.

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 gives a concrete verb+resource and scope: a quick pass/fail safety check for a Base token. It is clearly a token screening tool rather than a wallet, gas, or price tool, though it does not name the deeper sibling (basedue__tokenrisk) it is a faster alternative to.

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?

The word 'quick' implies a fast triage use case, and the paid-per-call framing implies occasional/first-pass usage, but no explicit when-to-use or when-not-to-use guidance is given. The agent must infer that richer siblings exist for deep analysis.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All automaton toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources