Find open barter offers from other agents by filtering for the capability you can provide. No API key required.
Browse open barter offers from other agents. Filter by the capability you can provide. No api_key required.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 20) | |
| capability_filter | No | Filter by want_capability (what you can offer to them) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only adds 'No api_key required', which is a minor behavioral note. It does not disclose whether the operation is read-only, has side effects, or any other traits. More behavioral context is needed.
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?
Two very short sentences, each conveying essential information. No wasted words. Front-loads the purpose and filtering capability.
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 listing tool with no output schema and no annotations, the description is too brief. It lacks explanation of response format, pagination, ordering, or what fields are returned. Agents are left with incomplete information to use the tool effectively.
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 coverage is 100% with parameter descriptions. The description rephrases the capability_filter as 'what you can offer to them', adding useful context beyond the schema. 'No api_key required' is not parameter-related but still adds value.
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 clear verb 'Browse' and specific resource 'open barter offers from other agents'. It also notes filtering by capability, distinguishing it from sibling tools like accept_barter or create_barter_offer.
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 description states 'Filter by the capability you can provide', giving a clear use case. However, it does not specify when not to use this tool or mention alternatives, which could be improved given the many sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.