MappaIQ

Create map

create_map

Create a brand-new, empty map (the top-level container that holds layers and pins). Use when the user wants a NEW map rather than a new layer inside an existing one — e.g. 'make a separate map for each broker', 'create a Grocers map'. After creating a map, add layers to it with create_layer (pass this map's name as mapName) and then add pins with add_comp/bulk_add_comps. Returns the new map's id and name.

Input Schema

Name	Required	Description
`name`	Yes	Name for the new map (e.g. 'David Zoller', 'Grocers').
`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."
`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.
`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.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so safety is covered; the description adds that the result is empty and what the creation kicks off downstream. It also discloses return values ('the new map's id and name') absent an output schema. It does not say what happens on duplicate names or where the map lands (root vs. folder), so not a full 5.

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, front-loaded with the definition before the when-to-use clause, then the workflow. Nothing is repetitive and every sentence carries distinct information.

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 create tool with full schema coverage, the definition covers purpose, triggering condition, downstream sequence, and return values. The only uncovered corner is placement/duplication semantics relative to map folders, which is a minor omission rather than a blocking gap.

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 'name' and the analytics-only 'context'/'llm_model' params are already fully documented; baseline 3 applies. The description's one extra hint — that create_layer takes this map's name as mapName — concerns a sibling's parameter rather than explaining this tool's own inputs.

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 ('Create a brand-new, empty map') and immediately defines what a map is ('the top-level container that holds layers and pins'), which separates it from create_layer and create_map_folder. An agent can distinguish it from every sibling 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?

Explicitly states when to use it versus the nearest alternative: 'Use when the user wants a NEW map rather than a new layer inside an existing one', reinforced with two concrete user utterances. It also sequences the follow-on tools (create_layer with this map's name as mapName, then add_comp/bulk_add_comps).

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?