Skip to main content
Glama

Lender position

get_lender_position
Read-onlyIdempotent

A lender's deposit, USDC in active loans, USDC available to withdraw, per-token limits, and every loan they funded with any repaid USDC or defaulted collateral they can claim.

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

Input Schema

NameRequiredDescriptionDefault
lenderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuine value by spelling out the composition of the response (balances, limits, funded loans, and claimable amounts), which is important given there is no output schema. It stops short of noting chain context or what happens for a non-lender address.

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?

A single sentence with no filler, and the most important item (the lender's deposit) is front-loaded. It is written as a noun-phrase fragment rather than a statement of what the tool does, which slightly weakens the opening.

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

Completeness3/5

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

With one parameter, no output schema, and full annotation coverage, the definition is close to sufficient — the return-field enumeration substitutes for the missing output schema. However, an agent still cannot tell whether a non-lender address errors or returns zeros, or whether pending/accrued interest is included.

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

Parameters2/5

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

Schema description coverage is 0% for the single required 'lender' parameter; the only constraint conveyed is the 0x-address regex in the schema itself. The description's phrase 'a lender's' implies the parameter identifies a lender but says nothing about whether the address must be an existing lender, which chain it belongs to, or checksum requirements.

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?

The description enumerates exactly what the tool returns — deposit, USDC in active loans, withdrawable USDC, per-token limits, funded loans, and claimable repayments/collateral — which makes the resource unambiguous. It lacks an explicit verb and never names the borrower-side sibling (get_borrower_loans) as the counterpart, so differentiation relies on the reader inferring it from the word 'lender'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no statement that the supplied address must actually be a lender, and no routing to get_borrower_loans for the borrower view. The enumerated fields only indirectly imply what questions this answers.

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.