Skip to main content
Glama

Prepare a lending deposit

build_deposit
Read-onlyIdempotent

Returns the unsigned transactions to deposit USDC for lending, optionally setting per-token lending limits in the same transaction (needed before a first deposit can be lent). Check get_risk_report for each token first.

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": {
      "amount_usdc": "<amount_usdc>",
      "lender": "<lender>"
    },
    "name": "build_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
lenderYes
limitsNo
amount_usdcYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark this readOnly/idempotent/non-destructive; the description adds the crucial behavioral fact that it only builds unsigned transactions and does not submit them, plus that limits are written in the same transaction. It does not discuss return shape beyond "unsigned transactions" or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the return value and action, followed by the prerequisite. No filler or restated boilerplate.

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?

No output schema exists, and the description at least characterizes the return as unsigned transactions; prerequisites and the optional limits path are covered. What an agent should do with the transactions afterward (simulate/sign/submit) is the remaining gap.

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?

Top-level schema description coverage is 0%, so the description must carry the load; it explains the purpose of the limits array (per-token caps, must be set before lending) but says nothing about amount_usdc units/format or what "lender" represents (depositor vs. on-behalf-of address). Nested asset/limit semantics are partly covered by the schema itself.

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?

States a concrete verb and resource: returns unsigned transactions to deposit USDC for lending. It also distinguishes itself from a pure limit-setting flow by noting limits can be bundled into the same transaction, though it never names build_set_limits explicitly.

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 ("Check get_risk_report for each token first") and a clear condition for supplying limits (needed before a first deposit can be lent). It stops short of saying when to skip this tool or which sibling to call next to submit the transactions.

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.