Skip to main content
Glama
Sign In

Fabrica (Sepolia testnet)

by land.fabrica
OverviewDiscussionsAdmin

Prepare a new property description

update_land_description

Prepare replacing a property's description with new plain text, up to 5000 characters (Sepolia Testnet). Checks first that the wallet holds at least 50% of the property (the contract's rule for this change), that the property backs no loan and that the text differs from the current one. The sign page opens the description editor with the text filled in, editable before saving; saving stores it and records it onchain. 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": {
      "description": "<description>",
      "wallet": "<wallet>"
    },
    "name": "update_land_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoProperty slug from the URL
walletYesThe wallet that holds the property and will sign (0x address). The sign page only lets this wallet sign.
tokenIdNoThe token ID of the property
descriptionYesThe property's new description, as plain text (up to 5000 characters). It replaces the current one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations say only that this is a non-readonly, non-idempotent, open-world call. The description goes well beyond them: it explains that nothing is sent, that a signRequest is stored and returned with a signLink, warnings and a 15-minute expiry, that the payload is null until signing, and that the server holds no keys.

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?

The key fact, that this prepares rather than sends, is front-loaded, and the sentence order follows the actual flow. Some phrasing is redundant, notably 'Prepared, not sent' being restated as 'nothing happens until then' and 'submits nothing', and the parenthetical Sepolia note interrupts the main clause.

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?

For a prepare-then-sign mutation with no output schema, the description covers preconditions, the exact return payload, its expiry, and where the human step happens. An agent can decide whether to call it and set expectations for the caller without further information.

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%, so slug, wallet, tokenId and description are already documented in the schema. The description restates the 5000-character limit and adds the useful note that 'wallet is the address that will sign', but contributes little else beyond what the schema already carries.

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?

The opening sentence gives a specific verb and resource: 'Prepare replacing a property's description with new plain text, up to 5000 characters.' That is enough to separate it from update_land_photos and update_trust_agreement 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 Guidelines4/5

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

The description spells out the three preconditions that gate success (wallet holds at least 50%, property backs no loan, text must differ from current), which is unusually strong when-to-use guidance. It stops short of naming an alternative tool for the case where those checks fail, so it is not a 5.

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