Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

basedue__approvals

List active ERC-20 approvals for a Base wallet, flagging unlimited ones. 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/approvals

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

Input Schema

NameRequiredDescriptionDefault
addressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / owner
      Removed value: -{
-  "type": "string"
-}
  2. Added

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does add genuinely useful context — a $0.01 USDC charge on Base and the x402 payment envelope in params._meta — but says nothing about what happens when the optional address is omitted, how 'unlimited' is signaled in the response, rate limits, or failure modes.

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?

The purpose is front-loaded in the first clause, followed by compact payment and transport details; no filler sentences. Slightly dense with three distinct concerns (purpose, price, endpoint) packed without structural separation.

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 simple one-parameter read tool with no output schema, the definition covers purpose, payment, and endpoint, which is most of what is needed. The gaps around optional-parameter behavior and the shape of the unlimited-approval flag leave an agent guessing at invocation and interpretation.

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?

The single parameter has 0% schema description coverage, so the description must compensate and largely does not. It implies the address is a Base wallet but never states the expected format (0x hex), nor what the tool defaults to when the optional address is not supplied.

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 ('List active ERC-20 approvals for a Base wallet') plus the notable behavior of flagging unlimited approvals. It is distinguishable from most siblings, though it never explicitly contrasts itself with the very similar basedue__allowance or txpreflight__allowance tools.

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: an agent can infer this is for auditing outstanding token approvals on a wallet. There is no statement of when to prefer it over basedue__allowance, basedue__tokenrisk, or txpreflight__allowance, and no prerequisites or exclusions are given.

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