Skip to main content
Glama

Prepare a deposit into the lending pool

deposit_to_lending_pool

Prepare depositing amountUsd in USDC into one tick of the DeFi lending pool (Sepolia Testnet). A tick sets the largest loan it funds (a share of a property's value, or a fixed dollar amount) and the longest loan length; with tick left out and several open, the answer lists them (ticks) so the person can choose. Interest is set by the pool, variable and not guaranteed, and deposits are at risk: a loan a borrower does not repay, and whose auction falls short, reduces the tick's value. A withdrawal is paid from funds the tick has not lent out; the rest waits until loans are repaid. Prepared, not sent: returns a signRequest (summary, warnings, signLink to fabrica.land, expiresAt 15 minutes out, payload null for now) and stores it so the sign page can load it. The person opens the link, signs in with that wallet and signs; nothing happens until then. The server holds no keys and submits nothing. wallet is the address that will sign.

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": {
      "amountUsd": "<amountUsd>",
      "wallet": "<wallet>"
    },
    "name": "deposit_to_lending_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolNoThe pool's address, when the network has more than one
tickNoThe pool tick: tick from the list this tool returns when tick is left out. A tick sets the largest loan it funds (a share of a property's value, or a fixed dollar amount) and the longest loan length
walletYesThe wallet that will sign (0x address). The sign page only lets this wallet sign.
amountUsdYesAmount to deposit in US dollars, paid in USDC (one USDC counts as one dollar)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false; the description goes far beyond by disclosing that nothing is submitted, the server holds no keys, the stored signRequest expires in 15 minutes with a null payload, and that deposits carry loss risk when a borrower defaults and an auction falls short. It also explains the withdrawal liquidity constraint (paid only from unlent funds). None of this is derivable from the annotations, and it does not contradict them — the financial risk described is not a destructive/mutating data operation.

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 one dense paragraph but front-loads the action, then risk, then the prepare/sign mechanics — a sensible order. Nearly every sentence carries decision-relevant information, though a few clauses (e.g. the repeated definition of a tick) are stated twice and could be tightened.

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 takes on the burden of describing the return value and does so precisely: signRequest with summary, warnings, signLink, expiresAt, and payload null. For a non-idempotent, open-world, human-in-the-loop mutation tool, it leaves nothing an agent needs to call it correctly or explain the flow to a user.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3, but the description adds cross-parameter meaning: tick is sourced from this tool's own list when omitted, wallet is specifically the signing address the sign page will honor, and amountUsd is paid 1:1 in USDC. These relational clarifications exceed the per-field schema text.

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 — 'Prepare depositing amountUsd in USDC into one tick of the DeFi lending pool' — and pins the network (Sepolia Testnet). It is plainly distinguishable from the sibling withdraw_from_lending_pool and from borrow_against_land, since the scope is 'prepare a deposit' rather than a loan or withdrawal.

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?

It gives clear conditional guidance for the ambiguous case: 'with tick left out and several open, the answer lists them (ticks) so the person can choose,' which tells the agent how to bootstrap a two-step interaction. It also explains the essential usage precondition that the deposit is only prepared, not executed, and requires the person to open the link and sign. It stops short of explicitly contrasting against withdrawn/borrow siblings, keeping it below 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.