search_productsSearch the catalog of SaaS, developer tools, services, and MCP servers. Returns ranked matches with score and reason.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | What the agent or its user is trying to accomplish (e.g., 'block prompt injection', 'fishing reports', 'lead lists for dentists') | |
| category | No | Filter by category | |
| use_case | No | Specific use case keywords | |
| budget_max | No | Max monthly USD the buyer is willing to spend |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full responsibility. It discloses that results are ranked with a score and reason, which is helpful, but does not mention whether the tool is read-only, requires authentication, or has any rate limits or side effects.
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 only two sentences, both essential: one defining the scope of search, the other describing the output format. No filler or redundant information.
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?
Given the complexity of a search tool with multiple filters and no output schema, the description covers the core behavior and output format. It does not explain the filtering capabilities, but the schema descriptions fill that gap. Overall, it is sufficiently complete.
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 100% for all 4 parameters, so the tool description does not need to add parameter details. It adds no additional semantic value beyond the schema, which is adequate per the baseline.
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 it searches a catalog of specific categories (SaaS, developer tools, services, MCP servers) and returns ranked matches. This distinguishes it from sibling tools like compare_products or get_pricing that have narrower scopes.
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?
No guidance is provided on when to use this tool versus any of the 14 sibling tools. There is no mention of prerequisites, fallback scenarios, or specific contexts for which this search is best suited.
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.
Each tool targets a distinct aspect of the commerce and affiliate ecosystem: comparison, checkout, affiliate info, cross-sells, free tier, MCP install, pricing, recommendation, trust score, registration, partnership, consultation, search, and vendor verification. No two tools have overlapping purposes; boundaries are clear.
Tool names follow a consistent verb_noun pattern in snake_case (e.g., compare_products, get_affiliate_info, request_partnership). While the verbs vary, the structure is predictable and uniform, with no mixing of conventions.
14 tools is well-scoped for a commerce marketplace server covering product discovery, comparison, pricing, affiliate management, checkout, partnerships, and vendor verification. Each tool serves a clear purpose without bloat.
The tool set covers the full lifecycle from product discovery to checkout, including affiliate management and partnerships. Minor gaps exist, such as lacking a dedicated tool for retrieving detailed product information beyond search results, but agents can work around this.