Skip to main content
Glama

Prepare a photo update

update_land_photos

Prepare a link that opens a property's photo editor on its page (Sepolia Testnet), where the owner adds, removes or reorders photos and videos from their own device and saves; files are not passed through this server. Checks first that the wallet holds at least 50% of the property and that it backs no loan, and reports how many photos it has now. 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_land_photos"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing that files never pass through the server, the server holds no keys and submits nothing, and the request is stored server-side until the sign page loads it. It also specifies the 15-minute expiry and that the payload is null for now, which an agent could not infer from any structured field.

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 purpose and the non-custodial guarantee are front-loaded and the whole thing is dense with useful detail. There is mild redundancy between 'Prepared, not sent' and the later sentence 'The server holds no keys and submits nothing', and the description is on the long side for a 3-parameter tool.

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 fully: it enumerates the signRequest fields (summary, warnings, signLink, expiresAt, payload) and explains the human-in-the-loop signing step. Combined with the stated eligibility checks, an agent has everything needed to call this correctly and explain the outcome.

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 the schema already documents slug, wallet and tokenId, and the description's note that 'wallet is the address that will sign' largely restates the schema text. It adds the meaningful constraint that the wallet must hold 50% of the property, but says nothing about when to use slug versus tokenId.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action (prepare a sign link) for a specific resource (a property's photo editor) and scopes it to Sepolia Testnet, so the agent can tell this apart from generic update tools. It never names the nearest sibling, update_land_description, so the photo-vs-description distinction must be inferred from the mention of 'photos and videos'.

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?

Preconditions are stated explicitly: the wallet must hold at least 50% of the property and back no loan. It also clarifies that this only prepares a request and that nothing happens until the human signs. It stops short of naming alternatives such as update_land_description or update_trust_agreement for other edit types.

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.