Skip to main content
Glama
Sign In

Fabrica (Sepolia testnet)

by land.fabrica
OverviewDiscussionsAdmin

Get my loans

get_my_loans
Read-onlyIdempotent

List the connected person's lending on Fabrica (Sepolia Testnet), across every wallet on their account: taken, the loans against their properties (active first, with maturity date, days to maturity, maturingSoon within 14 days, payoff today and its as-of time, APR and the property page where it is repaid); made, loans they funded; deposits, their position in the DeFi lending pool (value at current pool prices, pending redemptions, pool page link); and counts of the loans they took. A loan between two of their own wallets appears under both taken and made. Prepares nothing: repaying and depositing happen on fabrica.land. Needs the connection's portfolio:read grant.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the required portfolio:read grant, the cross-wallet aggregation scope, the double-counting rule for self-to-self loans, the 14-day maturingSoon threshold, and the as-of timestamp on payoff figures. These are exactly the behavioral details an agent cannot infer from structured fields.

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?

Front-loaded with verb and resource, then a dense but purposeful enumeration of the returned categories, closed by two short constraint sentences. The middle sentence is long and list-heavy, but each clause (maturity date, days to maturity, payoff as-of time, APR, property page) carries distinct information rather than filler.

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?

With no output schema, the description carries the full burden of describing return values, and it does so field-by-field for all four categories, including the pool page link and pending redemptions. Auth requirements and the no-side-effects guarantee are also stated, leaving nothing an agent needs before calling it.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It instead spends its words on return-value semantics, which is the right allocation.

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?

Opens with a specific verb and resource ('List the connected person's lending on Fabrica') and immediately scopes it to 'across every wallet on their account', then enumerates the four result categories (taken, made, deposits, counts). This clearly separates it from siblings like get_land_portfolio or get_fabrica_loan_book, which are not account-scoped lending views.

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 a clear boundary statement — 'Prepares nothing: repaying and depositing happen on fabrica.land' — telling the agent this is read-only and where mutations live, plus the required portfolio:read grant. It does not explicitly name which sibling to use instead for a single loan or a market-wide view, so it stops short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fabrica (Sepolia testnet) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources