Skip to main content
Glama
Sign In

Vectorial Data Terminal: Hyperliquid, Polymarket & yield for AI agents

by com.vectorialdata
OverviewDiscussionsAdmin

earn_usdc_deposit

Lend USDC on Base in our Earn USDC vault (Morpho, Gauntlet USDC Prime) from your trading wallet's address on Base — move USDC there first with move_funds perps → earn_usdc. No entry fee; the vault keeps 20% of the yield. Owner-signed Base transactions (gas ~1¢ in USDC): submit_operation needs owner_public_key. Returns operation_id + signatures_needed[]: sign EACH step with the signer it names — 'owner' = your OWNER P-256 key over payload_b64 (decode it and check every verify line against YOUR records first), 'trading_key' = your trading key over typed_data (EIP-712) — then submit_operation within 5 minutes.

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

Input Schema

NameRequiredDescriptionDefault
allNotrue = lend all your USDC on Base except what gas needs
amount_usdNoUSDC on Base to lend

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only mark it as a non-idempotent, open-world write; the description adds the economics (no entry fee, 20% of yield kept), the gas cost (~1¢ in USDC), the owner-signed transaction model, and the exact failure-relevant constraint of a 5-minute signature window. It further discloses the return contract (operation_id plus signatures_needed[]) and how each signer type must be applied, which no annotation conveys.

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?

Purpose and funding route are front-loaded, and every clause carries operational information about fees, signing, or deadlines. It is nevertheless one dense run-on paragraph mixing economics, signing protocol, and expiry, which costs some readability.

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

Completeness5/5

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

For a two-step prepare/submit flow with no output schema, the description supplies the return shape, the signer-to-payload mapping, the verification step, and the submission deadline. An agent has everything needed to call it and act on the result correctly.

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%, and the description's 'lend all your USDC on Base except what gas needs' essentially restates the schema's own text for the all flag. The amount_usd parameter gets no additional meaning such as minimums or precision, so the baseline of 3 is appropriate.

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?

States a specific verb and resource: lend USDC on Base into the Earn USDC vault (Morpho, Gauntlet USDC Prime), funded from the trading wallet's Base address. It also implicitly separates itself from earn_usdc_withdraw and earn_hlp_deposit by naming the vault and the funding route, so an agent can pick it without inspecting schemas.

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?

Gives an explicit prerequisite and ordering: move USDC there first with move_funds perps → earn_usdc, then this tool, then submit_operation within 5 minutes. It does not state the negative case (use earn_usdc_withdraw to exit) or what to do if funds are already on Base, so guidance is strong but not exhaustive.

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

All Vectorial Data Terminal: Hyperliquid, Polymarket & yield for AI agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources