Search the catalog of KYA-verified sellers. Public — no auth needed.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | good | service | api | tool | |
| query | No | keyword (title/description) | |
| category | No | ||
| verified_only | No | default true |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool is public and requires no auth, but it does not describe return format, pagination, or any rate limits. Additionally, the phrase 'catalog of KYA-verified sellers' may be slightly ambiguous given the verified_only parameter, but there is no clear contradiction.
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 two sentences, front-loaded with the primary action, and every word earns its place. It is appropriately concise with no redundant filler.
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?
The tool has 4 optional parameters and no output schema, so the description should provide more context about what results to expect or how the search behaves. It only mentions the resource and public access, leaving out important details like result ordering, filters, or pagination, making it incomplete for a search tool.
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 75%, and the description adds no additional parameter meaning beyond what the schema already provides. The category parameter has no description in the schema, and the description does not compensate for that gap, so it adds limited 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 clearly states the action ('Search') and the resource ('the catalog of KYA-verified sellers'), giving a specific verb+resource. It distinguishes from sibling tools like get_listing by the verb, but does not explicitly reference alternatives, so it's clear but not fully differentiated.
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 provides a clear usage context ('Search the catalog') and an important prerequisite ('Public — no auth needed'). However, it does not mention when not to use this tool or point to alternatives such as get_listing for retrieving a specific listing, so guidance on tool selection 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.
Most tools target distinct resources, but fx_rates and kzt_rates both provide exchange rate data and could be easily confused. The remaining tools are clearly separated by purpose.
Tool names are consistently snake_case, but follow two patterns: verb_noun (get_listing, search_listings) and noun_noun (fx_rates, kzt_rates, lei_lookup), with 'weather' being a bare noun. This mix is readable but lacks a unified convention.
With 10 tools, the count is within the ideal range. However, several tools (weather, exchange rates, parcel tracking) seem tangential to a 'marketplace' server, making the scope slightly broad.
The marketplace core is covered with search_listings/get_listing and verify_agent, but there are gaps such as no direct agent search or way to create/update listings. The Kazakhstan-specific utilities are each complete in isolation, but the overall surface lacks a cohesive lifecycle.