Skip to main content
Glama

Arc yield

arc_yield

Yield on Arc before you deposit: every lending vault Circle Earn Kit lists on Arc (Morpho Vault V2) with its rate (Circle's figure), size, how much a depositor can actually withdraw at this block (read on chain), where its money is lent and a 24 h trail of what could be withdrawn. Refreshed every 15 minutes. $0.003 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": "arc_yield"
  }
}

Input Schema

NameRequiredDescriptionDefault
vaultNooptional: one vault address (0x...) instead of the whole board
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.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does substantial work: 15-minute refresh cadence, an on-chain read for withdrawable amounts, a $0.003 per-call price, accepted payment assets (USDC on Arc/Base/Solana, XNT on X1), and the x402 terms-then-pay handshake. It omits failure behaviour (what a rejected or expired payment returns) and any pagination or result-size expectations, which keeps it from a 5.

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 value proposition and data inventory are front-loaded in the first sentence, with payment mechanics trailing, so an agent gets the gist immediately. The first sentence is long and comma-chained, which costs a bit of readability, but almost every clause carries distinct information.

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?

There is no output schema, so the description must describe returns, and it does list the returned fields plus a freshness guarantee. What remains unstated is the response shape (single object vs. array of vaults) and how the 24h trail is encoded, which for a paid data endpoint an agent may want to know before spending $0.003.

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 100%, so both parameters are already documented in structured form, giving a baseline of 3. The description does add real meaning for `payment` by explaining the two-call terms-sign-pay flow and that the purchase completes inside the call, but it adds nothing about `vault` beyond what the schema already states.

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

Purpose5/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 ('Yield on Arc ... every lending vault Circle Earn Kit lists on Arc (Morpho Vault V2)') and enumerates the exact data returned: rate, size, block-level withdrawable liquidity, lending destinations, and a 24h trail. That is specific enough to separate it from neighbours like arc_pools or arc_grow without opening the schema.

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?

'Yield on Arc before you deposit' establishes the decision context (pre-deposit due diligence), and the closing sentences spell out the exact invocation sequence: call without `payment` for terms, sign, call again. It does not name a sibling alternative or state when this is the wrong tool versus arc_pools, so it stops short of a 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