Skip to main content
Glama
Sign In

Fabrica (Sepolia testnet)

by land.fabrica
OverviewDiscussionsAdmin

Get property map image

get_land_map_image
Read-onlyIdempotent

Get a static map image of a property on Fabrica showing its parcel boundary (or a pin marker if no boundary is available). Returns an inline image. Supports dark/light themes and custom dimensions.

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

Input Schema

NameRequiredDescriptionDefault
slugNoProperty slug from the URL
themeNoMap theme (default: 'dark')
widthNoImage width in pixels (100-1280, default 640)
heightNoImage height in pixels (100-1280, default 640)
tokenIdNoThe token ID of the property

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world traits, so the description only needs to add context. It does: it discloses that the return is an inline image, that a pin marker substitutes when no boundary exists, and that theme and dimensions are adjustable — useful operational detail beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the primary purpose, then return format, then options. No filler and nothing repeated from the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only image tool with no output schema, the description covers what comes back (inline image), the visual fallback, and customization options. The only missing piece is guidance on which identifier (slug or tokenId) to supply, since neither is marked required.

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 five parameters including theme bounds and size ranges are already documented in the schema. The description reinforces theme and dimension support but says nothing about slug versus tokenId, which is the one genuinely ambiguous part given required=0.

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?

States a specific verb and resource ('Get a static map image of a property on Fabrica') and clarifies the visual content (parcel boundary or pin fallback). It implicitly distinguishes itself from portfolio-level mapping, though it never names get_land_portfolio_map_image or get_land_boundary as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the tool name and the singular 'a property', but there is no explicit when-to-use versus get_land_boundary or get_land_portfolio_map_image, and no statement of when NOT to call it (e.g., when no imagery exists).

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