Skip to main content
Glama

Borrower's loans

get_borrower_loans
Read-onlyIdempotent

Every loan a wallet has opened, with status (active, partially_repaid, repaid, defaulted), buyback remaining and time until due.

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": {
      "borrower": "<borrower>"
    },
    "name": "get_borrower_loans"
  }
}

Input Schema

NameRequiredDescriptionDefault
borrowerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real value by disclosing the returned dimensions and the four status states, but says nothing about ordering, pagination or size limits for what could be an unbounded list, and has no output schema to lean on.

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?

One tight sentence with no filler, front-loaded on scope and followed by the payload contents. It is a fragment rather than a sentence with a verb, which is acceptable but slightly less scannable than an explicit 'Returns ...' construction.

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?

For a read-only single-parameter list tool whose annotations cover safety, the description tells an agent enough about what comes back to decide to call it. It is still thin on the operational side: no pagination, no empty-result behavior, and no hint that results span closed/defaulted loans as well as active ones.

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?

One required parameter at 0% schema description coverage, so the description must carry the meaning. Saying 'a wallet' implies the argument is a wallet address, but it never states the 0x-address format, whose address it is (borrower vs. connected account), or what happens with an address that has no loans.

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 the resource ('Every loan a wallet has opened') and enumerates the returned fields (status values, buyback remaining, time until due), so an agent can tell this is a portfolio-level read. It never explicitly contrasts with the singular get_loan sibling, but the 'every loan' scope is clear enough to differentiate.

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

Usage Guidelines3/5

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

Usage is only implied: fetch this to see a wallet's loan book. There is no explicit when-to-use, no when-not, and no named alternative for a single loan lookup or a quote before borrowing. An agent can infer the case but gets no routing help.

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.