Skip to main content
Glama
multimedia-search-mcp

multimedia-search-mcp

list_providers

Lists registered multimedia search providers and indicates whether each is configured, letting you verify available sources without network requests.

Instructions

Lista los proveedores registrados y si están configurados.

No realiza peticiones de red.

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": "list_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. The negative constraint 'No realiza peticiones de red' is genuinely useful operational context (cheap, local, no rate-limit exposure), but it omits whether the call is strictly read-only, what permissions are needed, or where the provider list comes from.

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

Conciseness5/5

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

Two short sentences, front-loaded with the result set and followed by the one behavioral constraint that matters. Nothing is redundant.

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

Completeness4/5

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

An output schema exists, so return values need not be described, and with no parameters the surface area is small. Only secondary details (permission requirements, whether 'configured' means credentialed vs enabled) are left unstated.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies.

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?

States a concrete verb and resource ('Lista los proveedores registrados') and adds the scope of the returned data ('si están configurados'). It does not explicitly distinguish itself from siblings like get_provider_status or get_search_capabilities, leaving the list-all vs single-provider distinction implicit.

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

Usage Guidelines3/5

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

The enumeration-with-configuration-state framing implies the right moment to use it (discovering which providers exist), but there is no explicit when-to-use, when-not, or named alternative such as get_provider_status.

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