Skip to main content
Glama

Drip vault

drip_vault
Read-onlyIdempotent

Free sample: https://apexfaucet.xyz/drip-vault/ ($0.002). Perpetual Drip Vault status and next drip. Does not trigger a drip. 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

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": "drip_vault"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description adds substantial context on top: a real per-call cost ($0.002 payable in USDC on Arc/Base/Solana or XNT on X1), a free sample endpoint, the x402 payment handshake, and the explicit assurance that no drip is triggered. That is exactly the payment/auth/side-effect information an agent cannot get from the annotations, and nothing contradicts them.

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 pricing and identity of the tool lead, followed by the payment procedure, so it is well front-loaded. The $0.002 figure appears twice (sample and per-call), and 'Not advice' / the sample URL add mild commercial noise, but the whole block is short and every clause is actionable.

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

Completeness4/5

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

For a paid, annotation-covered, single-parameter tool this covers the critical unknowns: cost, currency options, the terms-then-pay sequence, and that the call is side-effect free. The only gap is that with no output schema present, the description gives just a one-line hint ('status and next drip') about what the paid response actually contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single `payment` parameter is already documented as a signed x402 payload. The description still adds operational meaning the schema lacks: that the first call should omit `payment` entirely to retrieve terms, and that `payment` is the second-phase argument supplied after signing.

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 names the resource ('Perpetual Drip Vault status and next drip') and states the negative scope ('Does not trigger a drip'), so an agent can tell it is a read of vault state rather than a claim/drip action. The verb is implicit in the noun phrase 'status' rather than stated outright, and no sibling tool is named, so it falls short of a 5.

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?

It gives an explicit procedural path: 'Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`.' That is clear when-to-use guidance for the two-step flow, plus a free sample URL. It does not name any alternative tool or state when a different vault tool would be a better choice, which keeps it below 5.

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