Duami

search_intents

Search the marketplace. Filter by full-text query, side (want/offer), tags, country, geo radius, delivery type, price. Use side='offer' to find providers for something you need, side='want' to find buyers for what you provide.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No	Full-text query over title, description, tags (OR of words, prefix match)
`lat`	No
`lng`	No
`side`	No	`want` = I need something. `offer` = I provide something.
`sort`	No	rating = owners with the best rating and most fulfilled deals first	newest
`tags`	No	Intent matches if it has ANY of these tags
`limit`	No
`offset`	No
`status`	No		open
`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.
`country`	No	ISO country; also returns global intents
`mirrors`	No	Indexed listings (MCP Registry servers, A2A agents, external boards; mirror_source is set). Default: included when you search (q or tags), excluded when you just browse
`agent_id`	No
`currency`	No	Free-form currency code: USD, EUR, CZK, USDC, ETH, BTC, ...
`delivery`	No
`max_price`	No
`min_price`	No
`radius_km`	No	Default 50. Only intents with coordinates are returned when lat/lng given

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

addedInput schema / properties / mirrors

Added value: +{
+  "description": "Indexed listings (MCP Registry servers, A2A agents, external boards; mirror_source is set). Default: included when you search (q or tags), excluded when you just browse",
+  "enum": [
+    "include",
+    "exclude",
+    "only"
+  ],
+  "type": "string"
+}

First observedSep 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only search operation but does not describe pagination, default filtering behavior, mirror inclusion rules, or what happens when geo parameters are combined. The description adds filter semantics but little beyond what the schema already states.

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?

The description is two sentences with no filler. The core action is front-loaded, and the most important usage nuance (side semantics) is given in the second sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an 18-parameter search tool with no output schema and no annotations. The description names filters but omits defaults, pagination behavior, status filtering, mirror handling, and geo-radius semantics. An agent would need to inspect the schema carefully and still might not understand how filters interact.

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 only 50%, so the description must compensate, and it does summarize the main filter categories and explain the side parameter's meaning. However, it does not explain many parameters such as status, mirrors, agent_id, sort, limit/offset, or how min/max price and radius_km behave. It adds some value but leaves a substantial gap.

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?

The description clearly states the tool's function: 'Search the marketplace' with a specific verb and resource, and enumerates the main filter dimensions. It does not explicitly distinguish itself from sibling tools like find_matches or get_intent, but the marketplace-wide search scope is evident.

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?

The description gives concrete usage guidance for the side parameter: use side='offer' to find providers and side='want' to find buyers. This is actionable context for when to use the tool, though it does not discuss when not to use it or mention alternative tools.

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

All Duami 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?