Skip to main content
Glama

Deposit USDC in the Curated Vault

build_curated_vault_deposit
Read-only

Deposit USDC into Steakhouse Prime USDC, a Morpho vault curated by Steakhouse Financial (about 4% a year, changes daily, compounds in the share price). Panda's fee: 0.05% once, inside the transaction. Withdraw any time. Returns unsigned transactions to sign in order (and as one EIP-5792 batch), simulated from the wallet, plus a sign_url for a human owner. Nothing is sent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wallet": "<wallet>",
      "amount_usdc": "<amount_usdc>"
    },
    "name": "build_curated_vault_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesThe wallet on Base that will sign (and that owns the positions).
amount_usdcYesUSDC to deposit (at least 1), in whole USDC, e.g. "25" or "0.5".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the fee (0.05% once, inside the transaction), the compounding mechanics, the exact return shape (unsigned transactions to sign in order, an EIP-5792 batch, simulated from the wallet, plus a sign_url for a human owner), and the crucial fact that 'nothing is sent'. This resolves the ambiguity created by readOnlyHint=true on a deposit builder.

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?

Front-loads the action and target, then layers economics, fees and return format in dense but information-bearing sentences. The parenthetical yield and fee clauses are slightly crammed, but every clause earns its place for a transaction-building tool.

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?

With no output schema, the description carries the burden of describing returns and does so fully: ordered unsigned transactions, batch format, simulation, sign_url, and the guarantee that nothing is transmitted. Combined with the 100%-covered two-parameter schema, an agent has everything needed to call and interpret it.

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%, so the schema already documents both wallet and amount_usdc including format examples and the 1 USDC minimum. The description adds no further parameter-level meaning, so the baseline 3 applies.

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 ('Deposit USDC into Steakhouse Prime USDC, a Morpho vault curated by Steakhouse Financial'), naming the exact product so it is distinguishable from the sibling build_vault_deposit and build_curated_vault_withdraw. An agent can identify the operation and the target vault 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?

Gives clear context for use: it describes the vault, its yield and that withdrawal is possible 'any time', which implicitly routes to build_curated_vault_withdraw for the opposite action. However, it never explicitly contrasts itself with build_vault_deposit (the non-curated vault) or states prerequisites such as the 1 USDC minimum or wallet funding requirements.

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