Loading ToolBench

Reading the current corpus…

hive-mcp-agent-quota MCP server · D · ToolBench

hive-mcp-agent-quota

Per-agent quota metering for the A2A network. Charges $0.001/check via x402, tracks consumption per agent DID, returns remaining quota. Inbound only. Hive Civilization.

2026-07-28+STREAMABLE_HTTP5 tools

53/100

Definition Quality55

Protocol Readiness72

Supportability38

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · evidence: Streamable HTTP

Current-spec patterns detected

Summary

Server implements 5 quota/metering tools with clear domain focus (x402 payment verification, quota tracking). Tool names follow verb_noun pattern (check, quote, topup, balance, stats). Descriptions are present and domain-specific (mention x402, USDC, Base L2). However, parameter descriptions are sparse or missing for several fields, and output schemas are not documented in the visible code. Error handling exists (verifyOnchain returns structured errors) but lacks recovery guidance for LLMs. No tool annotations (readOnlyHint/destructiveHint) despite clear risk distinctions (READ_ONLY vs WRITE). Schema completeness is moderate, input params have types but descriptions are minimal.

Tools (5)

quota/balanceread only50/100

Get current quota balance for an agent DID. No payment required.

quota/checkwriteauth50/100

Check remaining quota for an agent DID. Requires x402 payment proof (USDC on Base L2). Returns remaining units after consumption.

quota/quoteread only50/100

Get a payment quote for quota check. Returns x402 envelope with nonce, amount, and payment instructions.

quota/statsread only50/100

Get quota system statistics for today (UTC). Returns check counts, topup counts, and distinct agent counts.

quota/topupwriteauth50/100

Top up quota units for an agent DID. Requires x402 payment proof (USDC on Base L2).

Issues (5)

HIGHtool ↗

Output schemas not documented. Tools return data (remaining units, x402 envelope, balance, stats) but response structure is not visible in source. LLMs cannot plan downstream calls without knowing what fields to expect.

quota/checkquota/quotequota/topupquota/balancequota/stats

HIGHtool-description ↗

Parameter descriptions are minimal or absent. Fields like 'nonce', 'chain', 'tx_hash', 'payer', 'signature', 'message' lack explanations of their purpose, format, or constraints. LLMs cannot infer whether to pass these or how to obtain them.

quota/checkquota/topup

MEDIUMtool-annotations ↗

No tool annotations despite clear risk profile. quota/check and quota/topup are destructive (WRITE, consume units, charge payment); quota/balance, quota/quote, quota/stats are read-only. Missing destructiveHint and readOnlyHint annotations prevent LLMs from reasoning about safety and retry semantics.

quota/checkquota/topupquota/balancequota/quote

Recommendations

Document output schemas for all 5 tools. Specify what fields quota/check returns (e.g., remaining_units, granted_units, tx_hash, timestamp), what quota/quote returns (nonce, amount_usdc, expires_at_ms, payment_instructions), etc. Include field types and descriptions.
Add detailed descriptions to payment-related parameters. For 'nonce': 'Unique payment nonce from quota/quote response. Valid for 5 minutes.' For 'tx_hash': 'Hex transaction hash of USDC transfer on Base L2 (0x-prefixed, 64 hex chars). Must be confirmed on-chain.' For 'signature': 'Optional ethers.js signature of the message field for payer verification. Format: 0x-prefixed hex string.'
Add tool annotations to the MCP tool registration. Mark quota/check and quota/topup with destructiveHint=true (they consume units and charge payment). Mark quota/balance, quota/quote, quota/stats with readOnlyHint=true. Mark quota/quote with idempotentHint=true (repeated calls return the same nonce/amount for the same unit_count).
Enhance error responses with actionable recovery steps. E.g., if verifyOnchain returns {ok: false, reason: 'underpaid', paid_usdc: 0.0005, min_usdc: 0.001}, wrap it as: 'Payment underpaid: sent 0.0005 USDC but 0.001 required. Call quota/quote to get a fresh nonce and amount, then retry with a new transaction.'
Constrain the 'chain' parameter. Replace the string parameter with an enum: {"type": "string", "enum": ["base"], "description": "Blockchain network. Currently only Base L2 is supported."}. This prevents invalid values and self-documents the constraint.

Score history

Overall score trend

First recorded score · v2 rubric

53/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	53	2026-07-28+	v2