Skip to main content
Glama
Sign In

MappaIQ

by com.mappaiq
OverviewDiscussions(1)Admin

Confirm listings still active

confirm_listings
Destructive

Mark Listings as still on the market (Confirmed date = today). Withdrawn listings are skipped. Ask the Broker before you confirm more than one.

Input Schema

NameRequiredDescriptionDefault
idsYesListing ids, at most 200.
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."
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

B3.4/5.0
Behavior3/5

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

With destructiveHint=true already declared, the description usefully adds that withdrawn listings are skipped (partial-success behavior) and the timestamp semantics. It does not explain why the operation is destructive or what side effects/irreversibility the agent should expect, leaving a gap against the annotation's severity.

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?

Three tight sentences with the core action front-loaded and supporting caveats after. Nothing is wasted, though the 'Ask the Broker' sentence reads as policy rather than invocation guidance.

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 a destructive-flagged single-action tool with no output schema and fully documented params, the description covers effect and skip behavior but omits return/confirmation feedback and the reason for the destructive flag. Adequate but with clear 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 ids, context, llm_model, and conversation_id. The description adds no parameter syntax or format beyond the schema; the only related hint ('more than one') loosely maps to the ids array cap.

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 (Mark), resource (Listings), and observable effect (Confirmed date = today), so an agent knows exactly what state change occurs. It is broadly distinguishable from siblings like close_listing or update_listing, but does not name any alternative to sharpen the distinction.

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?

Provides a real usage constraint – 'Ask the Broker before you confirm more than one' – and notes that withdrawn listings are skipped, which implies partial-success scoping. However, it gives no guidance on when to prefer this over sibling tools like update_listing.

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