MappaIQ

Draw zone

add_zone

Draw a circular zone (a polygon area) on the map centered on the given latitude/longitude. Coordinates are required — place names are not looked up. Use this instead of add_comp when the user wants an area rather than a single pin.

Input Schema

Name	Required	Description
`name`	Yes	Zone name shown on the map (e.g. 'Waxahachie', 'North Dallas target area')
`notes`	No	Optional notes about the zone.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`layerId`	No	Layer ID to add the zone to. If omitted, the user's first layer is used.
`latitude`	Yes	Latitude in decimal degrees (-90 to 90). Required — addresses are not geocoded.
`zoneType`	No	Zone label: 'Search Area', 'Target Zone', 'Market Boundary', 'Comp Zone', 'Exclusion Zone', or 'Custom'. Default 'Search Area'.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`longitude`	Yes	Longitude in decimal degrees (-180 to 180). Required — addresses are not geocoded.
`radiusMiles`	No	If set, forces a circle of this radius in miles instead of the real boundary. Leave unset to use the place's actual outline. Default circle is 2 miles.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/safe profile is known. The description adds one useful behavioral constraint ("place names are not looked up"), but does not disclose what the call creates/returns or side effects. Adequate but thin on top of the 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 tight sentences with no filler, and the core action plus its scoping constraint are front-loaded ahead of the sibling routing. Every sentence earns its place.

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 10-parameter write tool the description covers purpose, the area-vs-pin decision, and the coordinate requirement, while annotations and a fully-documented schema carry the rest. The only minor gap is that with no output schema it does not indicate what the tool produces.

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 the schema documents all ten parameters in detail. The description only reinforces the required-coordinates constraint already stated in the latitude/longitude schema entries, adding little beyond what the schema provides. Baseline 3 is appropriate.

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 ("Draw a circular zone ... centered on the given latitude/longitude") and explicitly contrasts itself with the sibling add_comp. An agent can distinguish this from add_comp and add_listing without opening a schema.

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

Usage Guidelines5/5

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

Names the alternative explicitly and the selecting condition: "Use this instead of add_comp when the user wants an area rather than a single pin." The when-to-use and when-not-to-use cases are both covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MappaIQ 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.

Resources

Need Help?