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

free_sample

Get a free one-line Base USDC yield recommendation for your amount and time horizon, with no payment or API key required.

Instructions

Free teaser: best Base USDC yield right now, one conclusion. No 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": "free_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
amountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose two useful traits — the result is a single conclusion rather than a list, and no payment/auth is required — but says nothing about data freshness beyond "right now", rate limits, whether results are cached, or what happens with invalid inputs.

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 single telegraphic sentence is front-loaded with the core payload (best Base USDC yield) and wastes almost nothing. The "Free teaser" framing is mildly promotional, and the extreme terseness is what causes the missing detail rather than verbosity.

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

Completeness2/5

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

For a tool with two undocumented parameters, no annotations, and no output schema, the description leaves an agent guessing about inputs and about what the "one conclusion" actually contains (APY? protocol? pool?). It answers only the coarsest question of what the tool is about.

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

Parameters2/5

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

Schema coverage is 0%, so the description must explain the two parameters (days, amount), yet it mentions neither. An agent cannot learn from this text whether amount is in USDC units, how days changes the horizon of the yield estimate, or that both are optional.

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?

"Best Base USDC yield right now, one conclusion" names a concrete resource (Base USDC yield) and the shape of the answer (a single recommendation), which is enough to separate it from a list-style sibling like yields or pools. It stops short of an explicit verb and never names or contrasts a sibling directly, so it is clear rather than differentiating.

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?

"Free teaser" and "No payment" hint at the condition for using it (no-cost preview) and implicitly suggest a paid or fuller alternative exists. However, no alternative is named, and there is no guidance on when to prefer this over yields or plan, so usage must be inferred.

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