Skip to main content
Glama
Sign In

MappaIQ

by com.mappaiq
OverviewDiscussions(1)Admin

List public maps

list_public_maps
Read-only

Browse the OPEN MARKETPLACE: every map any MappaIQ user has published as Public. This reaches beyond the connected account — brokers and owners across the industry publish their listing portfolios here, and any connected agent can read them. Returns each public map's name, owner (with their public profile URL), pin/layer counts, and a browser link to the map's public page (pageUrl). Optional keyword filters by map or owner name. Use search_public_listings to query the pins themselves.

Input Schema

NameRequiredDescriptionDefault
contextYesExplain 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."
keywordNoFilter maps by map name or owner name (case-insensitive substring).
llm_modelYesThe 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_idNoPass 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.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine context beyond that: the marketplace scope spans accounts, it enumerates returned fields (name, owner profile URL, pin/layer counts, pageUrl), and notes the optional keyword filter. No auth or rate-limit detail, but the added value is real.

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?

Front-loaded with the core purpose, followed by scope, return fields, and the routing hint — a sensible order. The 'brokers and owners across the industry publish their listing portfolios here' clause is somewhat promotional filler but the overall density is acceptable.

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?

No output schema exists, so the description helpfully enumerates the return fields and provides a pageUrl link. Scope and the pin-level alternative are covered. The meta-parameters (context, llm_model, conversation_id) are self-documented in the schema, leaving only minor gaps.

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 fully documents all four parameters including keyword, context, llm_model, and conversation_id. The description's mention of 'optional keyword filters by map or owner name' merely restates the schema, so the baseline of 3 applies.

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 ('Browse the OPEN MARKETPLACE: every map any MappaIQ user has published as Public') and immediately scopes it against the connected account, which distinguishes it from the sibling list_maps. An agent can tell what it returns and how it differs from other list tools.

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?

Explicitly routes the pin-level query to the alternative ('Use search_public_listings to query the pins themselves') and implies the connected-account alternative via 'reaches beyond the connected account.' It gives clear context but never names list_maps explicitly or states when this tool should not be used.

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

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