Skip to main content
Glama
Universal Web Retrieval MCP

Universal Web Retrieval MCP

list_providers

Lists search/fetch providers with capabilities, configured and enabled status, chain position, active modes, and fetch policies so you can choose providers for web_search/web_fetch.

Instructions

List every provider this server knows: capabilities (search/fetch), whether it is usable right now (configured / key present), whether it is enabled, and its 1-based position in each active chain. Also reports the active search mode (failover/fanout), the fan-out fan width/grace, and the fetch policy (private-network access, block-page detection, extract limit). Never returns key values. Use it to decide what to pass in web_search/web_fetch providers.

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
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose behavior the schema cannot: it declares that key values are never returned, that usability is reported as configured/key-present, and that chain positions are 1-based. It does not explicitly state the call is side-effect free, but 'List' plus the absence of any mutation language makes read-only behavior clear.

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

Conciseness4/5

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

Three sentences, front-loaded with what is listed and followed by the mode/policy details and security note. The enumeration of returned fields is somewhat redundant given a separate output schema exists, but it is dense and free of filler.

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

Completeness5/5

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

For a no-parameter, read-only discovery tool with an output schema, this covers purpose, invocation rationale, and the security-relevant constraint that key values are withheld. Nothing an agent needs in order to call it correctly is missing.

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?

There are zero input parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It helpfully notes that the output is oriented toward the `providers` argument of sibling tools, which gives the listed data a purpose rather than just describing fields.

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

Purpose5/5

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

States a specific verb and resource ('List every provider this server knows') and enumerates exactly what is returned: capabilities, usability, enabled state, and chain position. It also distinguishes itself from the siblings by naming the `providers` parameter of web_search/web_fetch, so an agent can tell why this tool exists next to them.

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

Usage Guidelines4/5

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

The closing sentence gives explicit guidance: 'Use it to decide what to pass in web_search/web_fetch `providers`.' That is a clear context for invocation. There are no exclusions or when-not-to-use notes, but for a zero-argument informational tool there is little ambiguity to resolve.

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

Deploy Server

Other Tools