Skip to main content
Glama
multimedia-search-mcp

multimedia-search-mcp

get_provider_status

Checks connectivity, authentication, and availability for a media search provider, returning reachable status with failure reasons to diagnose issues before running searches.

Instructions

Comprueba conectividad, autenticación y disponibilidad del proveedor.

Devuelve reachable: false con el motivo si no responde; no lanza error salvo que el proveedor solicitado no exista.

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_provider_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does so well: it discloses that failure is reported as reachable: false with a reason rather than an exception, and that the only error path is a nonexistent provider. That is exactly the kind of error-semantics detail an agent needs. It stops short of noting cost, latency, or side effects of probing authentication.

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, result behavior front-loaded after the purpose statement, with no filler. Everything stated is operationally useful.

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?

A simple one-parameter tool with an output schema, so return-shape obligations are light, and the error behavior is covered. The remaining hole is the meaning of a null/omitted provider, which is central to invoking it correctly.

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 provider parameter is nullable with a null default. The description refers to 'el proveedor solicitado' and to erroring when it does not exist, but never explains what happens when provider is omitted (e.g. check all providers vs. a default). That is the key ambiguity an agent would face here.

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 description gives a specific verb set (checks connectivity, authentication, availability) against a specific resource (the provider), which is far more than a restatement of the name. It does not name any sibling such as list_providers or get_search_capabilities, so the boundary with those tools is left 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?

Usage is implied: this is the health/diagnostic probe for a provider, which an agent can infer from 'conectividad, autenticación y disponibilidad'. There is no explicit when-to-use versus list_providers or get_search_capabilities, and no statement that it is a read-only preflight check before search_media.

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