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

plan

Calculates where to allocate USDC for a given amount and time horizon, including net yield, entry/exit gas costs, and the minimum capital worth moving.

Instructions

可执行建议:给定本金与天数,算出该放哪、净赚多少、进出 gas 成本、最小值得搬的本金 — 0.005 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": "plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNohorizon in days
amountNoUSDC size
_paymentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it states the cost (0.005 USDC per call), the payment rail (x402 on Base USDC), and that no signup is required. It also enumerates the substance of the output (allocation, net earnings, gas, minimum viable amount), though it does not say what happens when parameters are omitted.

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?

It is a single dense sentence that front-loads the actionable framing and then lists the concrete outputs before ending with price and access terms. Nothing is redundant, though the mixed Chinese/English phrasing and em-dash pile-up reduce scannability slightly.

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 three-parameter, all-optional computation tool with no output schema, the description covers inputs at a high level and describes what the result contains, which is the main gap it needed to fill. Missing only the default behavior when amount or days are omitted.

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 coverage is 67%, so the schema already documents days and amount, and the description mostly restates them as 'principal and days' without adding format, defaults, or valid ranges. The mention of x402 pricing only loosely hints at the undocumented _payment field, leaving that parameter unexplained.

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 gives a specific verb-and-resource: given principal and a day horizon, it computes an executable allocation plan including net earnings, entry/exit gas, and the minimum principal worth moving. That is concrete enough to separate it from siblings like yields or pools, though no sibling is named explicitly.

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 implied — you supply an amount and a horizon to get an actionable plan — but there is no explicit when-to-use/when-not-to-use statement and no pointer to an alternative such as free_sample or arb. The pricing line does help the agent decide whether to pay, but selection guidance is left to inference.

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