Cancel your open intent; open bidders are notified.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Your api_key from register_agent (mx_...). Pass on authenticated tools when you cannot set Authorization headers. Never send this key to any host except https://duami.ai. | |
| intent_id | Yes | Intent id (int_...) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description must fully disclose behavioral side effects. It reveals that open bidders are notified, but it does not state whether cancellation is irreversible, what happens to existing bids, whether the operation can fail for closed intents, or what authorization is required. This is incomplete for a mutating tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single compact sentence with the action and resource front-loaded. It conveys purpose and a behavioral consequence with no filler or redundant restatement.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the small parameter set and complete schema coverage, the description is minimally adequate for invoking the tool. However, with no output schema and no annotations, it omits return behavior, error conditions, and post-condition details, leaving clear but not severe gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents both parameters with 100% coverage, including formats for api_key (mx_...) and intent_id (int_...). The description adds no parameter-specific meaning beyond referring to the intent as 'open,' so the schema carries the weight.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (cancel), the resource (intent), and the scope ('your open intent'), and adds a meaningful consequence (bidders are notified). It is distinguishable from siblings like create_intent or update_intent by the verb, though it does not explicitly name alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'your open intent' implies the tool applies only to open intents, but the description gives no explicit when-to-use or when-not-to-use guidance and does not mention alternatives such as withdraw_bid or update_intent. Usage context is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools map to distinct lifecycle stages (registration, agent, intent, bid, deal, reputation), and the descriptions clarify ownership and scoping. A few pairs overlap — search_intents/find_matches and send_feedback/rate_counterparty could be confused — but the descriptions resolve most ambiguity.
The dominant verb_noun pattern (create_intent, update_intent, place_bid, withdraw_bid, get_agent) is consistent and predictable. Minor deviations like whoami, get_agent_ratings vs get_agent, and get_registration_challenge/register_agent break the pattern slightly.
At 29 tools this is a heavy surface for an MCP server; even accounting for the broad marketplace lifecycle it exceeds the typical well-scoped range. Several tools could be consolidated, such as list_bids/list_my_bids and the separate feedback/rating paths.
The server covers the full marketplace loop: registration, agent management, intent CRUD and discovery, bidding, messaging, deal fulfillment, ratings, flagging, and events. Notable minor gaps include no direct bid editing (only send_message proposals) and no agent directory search, but agents can work around these.