Search public EDC catalog listings by brand, category, or query. Verify product pages for prices and configurations before purchase.
Search currently available public EDC catalog listings. Prices may represent different configurations; verify the product page before comparing or purchasing.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | ||
| limit | No | ||
| query | No | ||
| category | No |
Changes observed during successful MCP inspections.
v0.3.0Input schema / additionalPropertiesAdded value: +falseInput schema / properties / api_keyRemoved value: -{
- "description": "Optional API key for authenticated access.",
- "type": "string"
-}Input schema / properties / brand / descriptionRemoved value: -"Filter by brand name (e.g., 'Spyderco', 'Benchmade', 'Olight', 'Magnus')"Input schema / properties / brand / maxLengthAdded value: +120Input schema / properties / brand / minLengthAdded value: +1Input schema / properties / category / descriptionRemoved value: -"Filter by product category. Options: knives, wallets, flashlights, pens, fidgets_haptics, multi_tools, watches, bags"Input schema / properties / category / enumAdded value: +[
+ "knife",
+ "fidget",
+ "flashlight",
+ "pen",
+ "wallet",
+ "multi_tool",
+ "patch",
+ "other"
+]Input schema / properties / limit / descriptionRemoved value: -"Number of results to return (default: 10, max: 25)"Input schema / properties / limit / maximumAdded value: +25Input schema / properties / limit / minimumAdded value: +1Input schema / properties / limit / typePrevious value: -"number"New value: +"integer"Input schema / properties / query / descriptionRemoved value: -"Search keyword to match against product titles (e.g., 'titanium knife', 'Olight flashlight', 'fidget spinner')"Input schema / properties / query / maxLengthAdded value: +120Input schema / properties / query / minLengthAdded value: +1v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that with the warning that prices may reflect different configurations and need verification on the product page. It still says nothing about result ordering, pagination, or what an empty result means.
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 tight sentences with no filler; the core purpose is front-loaded and the reliability caveat follows immediately. Every sentence earns its place.
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?
No output schema exists, so the description would ideally say something about the shape or reliability of returned listings, and it does partially via the price-configuration warning. However, four undocumented parameters and no statement about result volume or ordering leave gaps for an agent that must decide how to constrain a search.
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 0% across four parameters, so the description carries the burden and adds essentially nothing: brand, query, category, and limit are never explained, nor is the max of 25 on limit or the meaning of the category enum values. The only faint signal is that searching is textual, which the tool name already conveys.
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?
States a specific verb and resource ("Search ... public EDC catalog listings") and narrows scope with "currently available", which distinguishes it from a general catalog dump. It does not explicitly contrast itself with siblings like get_latest_drops or check_availability, so an agent must infer the boundary.
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?
Usage is implied by "search" and the caveat "verify the product page before comparing or purchasing" hints that results are not authoritative for purchase decisions. There is no explicit when-to-use or when-not-to-use guidance, and no sibling tool is named as the alternative for browsing new drops or checking stock.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.