Skip to main content
Glama
multimedia-search-mcp

multimedia-search-mcp

get_search_capabilities

Retrieves supported search types and media categories for the current provider configuration, including indexer filtering and participation details, so callers can choose valid search parameters.

Instructions

Devuelve los tipos de búsqueda y categorías que admite la configuración actual.

Por tipo de contenido indica el modo (filtered/general), las categorías aplicadas y, por indexador:

indexers_supporting: anuncia exactamente la categoría (soporte declarado).
indexers_inferred: no la anuncia, pero sí un padre o descendiente
    (compatibilidad inferida por jerarquía, no confirmada: Prowlarr
    puede consultarlo o no).
indexers_participating: a quiénes consultará Prowlarr con certeza
    (en modo general, los habilitados; con filtro, solo los que
    declaran la categoría). Participar no implica devolver resultados.
indexers_unknown_state: habilitación desconocida; no cuentan como
    participantes.
participation_known: true solo si se conoce el estado de participación
    de todos los indexadores relevantes (listado leído y ninguno en
    indexers_unknown_state); no implica que haya participantes.
indexer_support: nivel por indexador (declared/inferred/none/unknown)
    con las categorías que lo motivan.

Las capacidades describen el filtrado del proveedor, no una clasificación semántica: movie/series/anime pueden solaparse (TV 5000 incluye 5070).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_search_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden. It does add genuine nuance about result semantics (participation does not imply results; inferred support is unconfirmed; unknown_state indexers are excluded), but it says nothing about read-only/authorization expectations, cost, latency, or caching for what appears to be a configuration-inspection call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main purpose is front-loaded in the first sentence and the field glossary is structured as a list, which aids scanning. However, the bulk of the text documents individual output fields, which is largely duplicative given an output schema exists, and the dense Spanish field-name glossary is heavy for a one-parameter read tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition thoroughly explains how to interpret the returned support/participation states, which is the genuinely non-obvious part. But with an output schema already present, that detail is partly redundant, while the one input parameter and the absence of any invocation context leave the definition incomplete on the input side.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single optional 'provider' parameter is never mentioned in the description, so the agent gets no information about what a provider value does, whether omitting it aggregates all providers, or how it interacts with the reported per-indexer capabilities.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource: it returns the search types and categories that the current configuration supports, plus the per-content-type mode (filtered/general). It is clear what the tool produces, but it never contrasts itself with siblings such as list_indexers or search_media, so the agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: nothing says to call this before search_media to check whether a filter will be honoured, and nothing states when-not to call it or which sibling to prefer. Usage is only implied by the word 'capabilities'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.