Skip to main content
Glama

Get loan book

get_fabrica_loan_book
Read-onlyIdempotent

Get the lending history of the Fabrica protocol as a distribution: loan counts and principal by status and provider, loan-to-value bands against today's property estimates, exposure by state and acreage, APR and duration spread, repaid and liquidated counts, originations by month for the last 12 months, and the largest loans with their property pages. Covers DeFi lending pool loans and historical peer-to-peer loans. Counts come from the loan records; where the pool data source's counters differ, both are shown.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fabrica_loan_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoOnly loans with this status (default all).
groupByNoAdds a groups table: loans, principal and outcome counts per state, provider, status, loan-to-value band or acre band.
largestNoHow many of the largest loans to list (default 10, max 25).
providerNopool: the DeFi lending pool. peer-to-peer: historical loans through the retired NFTfi integration. Default all.
sinceDaysNoOnly loans started in the last N days (default: the whole history).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: counts derive from loan records, and where the pool data source's counters disagree, both values are shown — an important reconciliation caveat an agent would otherwise not know.

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 a single dense sentence front-loaded with the core purpose, and each clause maps to real output content rather than filler. The long enumeration is heavy but almost every item earns its place by describing a returned section.

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?

There is no output schema, so the description must carry the return-value burden — and it does, itemizing every section the response contains (counts, principal, LTV bands, exposure, APR/duration spread, repayments, liquidations, monthly originations, largest loans with property pages). Nothing essential to calling or interpreting the tool is missing.

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% with enums on status, groupBy and provider, so the schema already carries the parameter semantics. The description alludes to the same dimensions ('by status and provider', 'by state and acreage') but adds no syntax, defaults, or interaction rules beyond what the schema documents — the baseline 3 applies.

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 gives a specific verb and resource ('Get the lending history of the Fabrica protocol') and enumerates the concrete distributions returned (loan counts, LTV bands, APR spread, originations by month, largest loans), so an agent knows exactly what this returns. It does not, however, distinguish itself from related siblings such as get_fabrica_lending_market or get_fabrica_stats, which an agent may hesitate between.

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?

The description states what data is covered ('Covers DeFi lending pool loans and historical peer-to-peer loans') but gives no when-to-use, when-not-to-use, or alternative-tool guidance. Nothing tells the agent why it should pick this over get_fabrica_lending_market or get_fabrica_stats for lending figures.

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.