Fabrica (Sepolia testnet)

Prepare a trust agreement update

update_trust_agreement

Prepare moving a property to the latest version of the Fabrica trust agreement (Sepolia Testnet). The trust agreement governs the trust that holds the land; the contract lets only a wallet holding at least 70% of the property change it. Checks first that the wallet holds that share and that the property backs no loan, and reports the version it is on now (get_land_trust_documents shows the text). The sign page shows the latest version's name and text and says when the property already uses it. Earlier versions are not offered. 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": {
      "wallet": "<wallet>"
    },
    "name": "update_trust_agreement"
  }
}

Input Schema

Name	Required	Description
`slug`	No	Property slug from the URL
`wallet`	Yes	The wallet that holds the property and will sign (0x address). The sign page only lets this wallet sign.
`tokenId`	No	The token ID of the property

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: explains that nothing is submitted, the server holds no keys, the request expires in 15 minutes, payload is null for now, and the signRequest is stored for the sign page. It also discloses the on-chain authorization check (70% share) and the no-loan precondition, which the annotations do not convey.

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 action and the core constraint, then layers preconditions, return shape, and the signing flow. Slightly redundant at the end, where 'nothing happens until then' and 'The server holds no keys and submits nothing' overlap in meaning.

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 return-value burden and does so precisely (summary, warnings, signLink, expiresAt, null payload) and explains the two-step prepare-then-sign flow. An agent has everything needed to call this correctly and set expectations with a user.

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 coverage is 100%, so all three parameters are already documented, including the wallet pattern and the sign-page restriction. The description's closing line 'wallet is the address that will sign' largely restates the schema rather than adding new meaning, and slug/tokenId are not elaborated.

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 and resource: preparing an update of a property's trust agreement to the latest Fabrica version, on Sepolia Testnet. It distinguishes itself from the read-only sibling by noting 'get_land_trust_documents shows the text' and by emphasizing it only prepares rather than sends.

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 explicit preconditions (wallet must hold at least 70% of the property and the property must back no loan) and states that earlier versions are not offered, plus the alternative for viewing document text. It does not explicitly say what to do when the property is already on the latest version beyond noting the sign page will report it.

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) tools Inspect

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.