Skip to main content
Glama
Sign In

Fabrica (Sepolia testnet)

by land.fabrica
OverviewDiscussionsAdmin

Prepare an offer

make_land_offer

Prepare an offer to buy a live property on Fabrica (Sepolia Testnet) at a USD amount paid in USDC, open for expiresDays (default 14). Checks first that the property is live and the wallet does not already hold it, and warns when the amount is far from Fabrica's estimate, when a listing is at or below it, or when the property is collateral for a loan. Prepared, not sent: returns a signRequest (summary, warnings, signLink to fabrica.land, expiresAt 15 minutes out, payload null for now) and stores it so the sign page can load it. The person opens the link, signs in with that wallet and signs; nothing happens until then. The server holds no keys and submits nothing. wallet is the address that will sign.

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": {
      "amountUsd": "<amountUsd>",
      "wallet": "<wallet>"
    },
    "name": "make_land_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoProperty slug from the URL
walletYesThe wallet that will sign (0x address). The sign page only lets this wallet sign.
tokenIdNoThe token ID of the property
amountUsdYesOffer amount in US dollars, paid in USDC (one USDC counts as one dollar)
expiresDaysNoDays the offer stays open (default 14)

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?

Goes well beyond the annotations: it lists the pre-flight checks (property live, wallet does not already hold it) and the warning conditions (amount far from estimate, listing at/below offer, property used as loan collateral). It also discloses key safety properties the annotations cannot express — no server-side keys, nothing submitted, 15-minute expiry, payload null for now — all consistent with readOnlyHint=false and idempotentHint=false.

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-loads the core action and flow, then the side effects and warnings; every sentence carries information. The prose is dense and slightly long, but no sentence is 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 takes on return-value duty and does so thoroughly: signRequest with summary, warnings, signLink, expiresAt, and payload null. Together with the check and warning behavior, an agent has everything needed to call it and explain the result to a user.

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 is 3, but the description adds real meaning: the USDC/USD 1:1 relationship, the 14-day default for expiresDays, and the crucial clarification that wallet is the signing address. It does not explain when slug versus tokenId is needed, which the schema also leaves loose.

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 concrete verb and resource ('Prepare an offer to buy a live property'), plus the chain (Sepolia Testnet), the pricing unit (USD paid in USDC) and the duration parameter. The 'Prepared, not sent' framing separates it cleanly from siblings like buy_land or accept_land_offer.

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?

The full two-step flow (prepare here, human signs on fabrica.land) is spelled out, including the explicit condition that nothing happens until signing, which tells an agent when this tool is the right entry point. It stops short of naming alternatives such as buy_land or accept_land_offer for direct purchases or accepting an existing offer.

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