Skip to main content
Glama
yg-base-mcp
by ufo1898

pools

Checks withdrawal health for Base yield venues by reporting available cash, utilization, and current withdrawal feasibility.

Instructions

Base 生息池提现健康度(池内现金 / 利用率 / 提现可行性) — 0.002 USDC per call (x402, Base USDC, no signup)

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

Input Schema

NameRequiredDescriptionDefault
_paymentNobase64 PAYMENT-SIGNATURE from a previous 402 challenge

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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: 0.002 USDC per call, x402 payment protocol on Base USDC, and no signup required — an agent knows it will hit a paywall. However it omits whether the call is read-only (implied but unstated), what happens if payment is absent, rate limits, and any hint of the response shape.

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?

One compact line that front-loads what the tool reports and appends the pricing/access condition. Every clause carries information; the only weakness is that the parenthetical metric list substitutes for a clear action verb.

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?

A low-complexity lookup with one fully-documented parameter and no output schema, so the description needn't explain return values in detail — and it does enumerate the three metrics returned. Still, with zero annotations the definition leaves gaps on read-only semantics, payment failure behavior, and which chain scope 'Base' covers beyond the name.

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% and the single optional _payment parameter is already documented as a base64 PAYMENT-SIGNATURE from a prior 402 challenge. The description adds only the surrounding x402 context, which corroborates rather than extends the schema — the baseline 3 for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and its content — Base yield-pool withdrawal health, covering pool cash, utilization and withdrawal feasibility — so an agent can tell it returns liquidity risk data. But there is no verb (fetch/read/query) and no differentiation from the sibling 'yields', which plausibly covers overlapping ground. Vague-but-informative rather than specific verb+resource.

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

Usage Guidelines2/5

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

No when-to-use guidance at all: nothing says to call this before a withdrawal, in place of 'yields', or alongside 'tokenrisk'/'wallet'. The only usage-relevant content is the x402 payment prerequisite, which is a cost/access condition, not a selection criterion. The agent must infer the use case from the topic alone.

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

Deploy Server

Other Tools