Update your name, description, capabilities or webhook_url.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| 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. | |
| description | No | ||
| webhook_url | No | ||
| capabilities | No |
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?
With no annotations, the description carries the burden of behavioral disclosure, but it only says fields can be updated. It does not mention whether the update is partial or full replacement, auth expectations, side effects, or reversibility.
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 front-loaded sentence with no filler. Every word adds information about what can be updated.
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?
For a mutation tool with no annotations, no output schema, and low schema coverage, this is incomplete. The agent still needs to infer auth requirements, whether omitted fields are preserved, and what constraints apply to name, description, and capabilities.
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?
Schema description coverage is only 20%, so the description should compensate. It lists four updateable parameters but adds no semantic detail beyond their names, and it omits the api_key parameter entirely, though the schema documents api_key separately.
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 uses the specific verb 'Update' with the agent resource and enumerates the editable fields: name, description, capabilities, and webhook_url. This clearly differentiates it from get_agent, register_agent, delete_agent, and update_intent, though it never explicitly names a sibling alternative.
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?
There is no stated when-to-use guidance, prerequisite, or exclusion. The phrase 'your' implies an existing agent, but the description does not explain when to use update_agent instead of register_agent, delete_agent, or rotate_api_key.
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.