Search all search-enabled catalogs from installed Stremio addons for a query, returning per-catalog matches with optional content type and result limit.
Search every installed addon catalog that declares search support.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| per_catalog | No | ||
| content_type | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does disclose one useful behavioral trait — only catalogs that declare search support are queried — but says nothing about auth requirements, result aggregation across catalogs, failure when zero catalogs qualify, or rate limits.
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?
A single front-loaded sentence with zero filler; the verb and scope constraint come first. Nothing in the sentence is redundant.
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?
An output schema exists, so return format need not be explained. But for a 3-parameter, unannotated tool with 0% parameter coverage, the description omits usage routing, parameter meaning, and behavioral context — leaving substantial gaps an agent must guess at.
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 neither the schema nor the description explains query, per_catalog (default 10), or content_type (default ''). 'Search' makes the query parameter inferable, but the per-catalog result cap and the content_type filter — both easy to misuse — are completely undocumented.
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 (search) and resource (every installed addon catalog declaring search support), with a meaningful scope qualifier that implies breadth beyond a single catalog. It is distinguishable from a single-catalog search, though it never names the sibling (stremio_search / stremio_browse_catalog) it competes with.
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 on when to choose this over stremio_search or stremio_browse_catalog, no preconditions, and no note about what to do if no installed catalog declares search support. The agent must infer that 'all catalogs' means the broadest search option.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.