Skip to main content
Glama

Get a loan against land

get_loan_against_land
Read-onlyIdempotent

Get one loan against a property on Fabrica: status (active, repaid, liquidated), provider, principal, APR, start, maturity, the full repayment and, for an active loan, the payoff today, with the borrower and lender wallets shortened and the property link. Give a property (tokenId or slug) for its active or latest loan, add loanId for a specific one, or give loanId alone to look it up across the network. otherLoans lists the property's other loans.

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_loan_against_land"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoProperty slug from the URL
loanIdNoThe loan id; with no property, the loan is looked up across the network
tokenIdNoThe token ID of the property

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered; the description adds real value by describing the response shape (shortened borrower/lender wallets, property link, payoff-today only for active loans, an otherLoans list). It stops short of describing empty-result or error behavior, so it is not fully exhaustive.

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 front-loads the purpose and the returned fields, then closes with the invocation rules, with no filler sentences. The return-field enumeration is dense but each item is decision-relevant; the trailing "otherLoans" sentence is slightly tacked-on in placement.

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?

With no output schema, the description carries the burden of explaining return values and does so field by field, plus it covers all three parameter combinations. What it omits is the no-results case and whether the payoff figure is a quote subject to change — small residual gaps for a read tool.

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 100%, so the baseline would be 3, but the description adds combination semantics the schema does not: which pairing of parameters yields the active/latest loan versus a specific loan versus a cross-network lookup. The tokenId-or-slug alternation is stated as an either/or, which the schema leaves as two independent optional fields.

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?

States a specific verb+resource ("Get one loan against a property") and enumerates exactly what is returned: status, provider, principal, APR, start, maturity, repayment schedule, and today's payoff for active loans. That field list distinguishes it from sibling aggregates like get_fabrica_loan_book or get_fabrica_lending_market without opening any schema.

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

Usage Guidelines5/5

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

Explicitly maps three invocation modes: property alone returns the active or latest loan, property plus loanId targets a specific loan, and loanId alone performs a network-wide lookup. The one ambiguity an agent would otherwise face — what a bare tokenId returns — is resolved in the text.

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.