Skip to main content
Glama

Drip sustainability

drip_sustainability
Read-onlyIdempotent

Simulate geometric declining Drip Vault emission and ApexRevenueSplit (50% 3x/day USDC faucet + 50% buyback) UBI coverage benchmarks against live APEX ecosystem telemetry. Not advice. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dailyRevenueUsd": "<dailyRevenueUsd>"
    },
    "name": "drip_sustainability"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
vaultApexNostarting Drip Vault tokens (default 50000000 APEX floor)
horizonDaysNosimulation horizon in days (1 to 3650, default 365)
eligibleUsersNodaily active claimants (1 to 1000000000, default 500)
annualDecayPctNoannual geometric drip decay percent (0.1 to 99, default 18.25)
faucetSharePctNopercent allocated to 3x/day faucet claims (1 to 100, default 50)
dailyRevenueUsdYesgross daily ecosystem/x402 revenue in USD (0.01 to 10000000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), and the description adds genuinely new behavioral facts: the exact price ($0.002/call), accepted payment assets and chains (USDC on Arc/Base/Solana, XNT on X1), and that the purchase completes inline when `payment` is supplied. It also disclaims 'Not advice.' Minor tension: a purchase completing inside a call annotated readOnlyHint=true is worth noting, but it is a payment for a read, not a data mutation, so it is not a true contradiction.

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?

Three tight sentences: purpose first, then cost/payment rails, then the procedural instruction. No filler, and the most action-critical information (the two-step payment flow) is placed last where it will be read as the call recipe. Only the parenthetical '50% 3x/day USDC faucet + 50% buyback' is dense enough to slow parsing.

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?

With no output schema, the description carries the burden of describing what comes back, and 'UBI coverage benchmarks' is a vague label for the result set. The payment mechanics — the hardest part of calling this tool — are well covered, so it is adequate, but an agent cannot predict the shape or units of the benchmark output.

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 100%, so the schema already documents all seven parameters, including defaults and ranges — baseline 3. The prose adds useful meaning for the `payment` parameter (two-step terms-then-signed-payload) but says nothing about the simulation knobs beyond what the schema states.

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 opens with a specific verb and resource: 'Simulate geometric declining Drip Vault emission and ApexRevenueSplit ... UBI coverage benchmarks against live APEX ecosystem telemetry.' It is clearly a forecasting/simulation tool, distinguishable from the arc_* chain-inspection siblings, though the heavy protocol jargon (Drip Vault, ApexRevenueSplit) assumes the agent already knows the domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage flow is stated explicitly and in order: 'Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`.' That removes most invocation ambiguity. It does not say when this simulation should be preferred over other analysis siblings or what inputs make a run invalid, but the operative guidance is concrete.

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