searchUnified read-only search across public Epinu projects and marketplace listings. Returns { id, title, url } results; call fetch with a returned id for the full document. Available without a token; public data only. Additive alias over projects_search and marketplace_listings_search.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and clearly states read-only, public data, and no token requirement. It also describes the return format. It does not mention pagination or rate limits, but for a simple search tool this is sufficient.
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 concise at three sentences, front-loads the purpose, and each sentence adds value with no redundancy.
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 single parameter, existence of an output schema, and no annotations, the description covers scope, availability, and follow-up actions. It could mention result limits or ordering, but overall it provides sufficient context.
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%, so the description should compensate by explaining the 'query' parameter. It only implies a text search without providing any semantics or syntax guidance, which is insufficient.
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 is a unified read-only search across public Epinu projects and marketplace listings, distinguishing it from sibling tools like projects_search and marketplace_listings_search.
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 explains it is a unified search that can be used without a token, and that results can be followed up with fetch. It implicitly provides context on when to use this tool over the individual search tools, though it lacks explicit when-not guidance.
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.
The search tools (search, projects_search, marketplace_listings_search) overlap significantly—search is explicitly an 'additive alias' over the other two, making them partially redundant. fetch, getting_started, and marketplace_listings_search are fairly distinct, but the search trio creates ambiguity about which to call for a given query.
Mixed conventions: projects_search and marketplace_listings_search follow verb_noun, but search, fetch, and getting_started are single words/varied patterns. Names are descriptive enough but lack a uniform verb_noun structure across the whole set.
Five tools is a reasonable size for a search/discovery-oriented server. The count feels slightly thin given the mention of several underlying operations (projects_get_deep_dive, marketplace_listing_get), but it's within a sensible scope for the apparent purpose.
Read-side coverage is decent: search, detail-fetch, and overview docs are all present. However, the server references get_deep_dive and get operations that aren't directly exposed as standalone tools, and there's no way to perform any writes/updates, leaving the surface feel like incomplete proxies for a broader API.