MappaIQ

Add pin

add_comp

Add a new record (pin) to a layer at the given latitude/longitude. Coordinates are required; an address is stored as text and never geocoded.

Input Schema

Name	Required	Description
`date`	No	Sale date
`name`	Yes	Comp name
`buyer`	No	Buyer name
`notes`	No	Additional notes
`price`	No	Sale price in dollars
`seller`	No	Seller name
`zoning`	No	Zoning classification
`acreage`	No	Acreage
`address`	No	Property address, stored as text on the pin. It is not geocoded — the pin goes at latitude/longitude.
`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`	Yes	Layer ID to add comp to
`flyerUrl`	No	Link to a marketing flyer PDF/page for this property — shown as a 'View flyer' card on the pin. Set from a source column clearly holding flyer links; if unsure whether a column is flyers, ask the user first.
`latitude`	Yes	Latitude in decimal degrees (-90 to 90). Required — addresses are not geocoded.
`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.
`externalId`	No	Optional stable ID from your source data (e.g. a spreadsheet Record #). Lets later imports upsert this record instead of duplicating it.
`customFields`	No	Any extra columns as a {fieldName: value} map — stored as real, filterable fields (e.g. {"Price per SF": "$18", "Tenant": "Acme"}). Use this for anything without a native slot above instead of cramming it into notes.
`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

B3.3/5.0

Behavior3/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description usefully adds the geocoding rule ('coordinates are required; an address ... is never geocoded'). Beyond that it says nothing about duplicates, upsert behavior, or the conversation_id handshake workflow, which the schema carries instead.

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?

Two tight sentences with the core operation and the key constraint (required coords, no geocoding) front-loaded. Nothing extraneous.

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

Completeness3/5

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

For an 18-parameter mutation tool with a nested object and no output schema, the description covers the essential operation but omits the conversation_id sequencing and the bulk-alternative context. Rich schema coverage compensates, keeping this adequate rather than complete.

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 already documents all 18 parameters, including the geocoding note and customFields. The description's coordinate/address statements largely duplicate schema content rather than adding new meaning, so the baseline 3 applies.

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 ('Add a new record (pin)'), names the container ('to a layer'), and specifies the required coordinate inputs. It is clear enough to distinguish from update_comp, though it does not explicitly contrast with sibling add/bulk_add tools.

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

Usage Guidelines2/5

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

No when-to-use guidance is given: it does not say when to prefer this over bulk_add_comps (many pins) or update_comp (existing pins). The address/geocoding note is behavioral, not usage guidance.

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?