Skip to main content
Glama

Dbnomics List Providers

dbnomics_list_providers
Read-onlyIdempotent

List all statistics providers available in DBnomics (80+), including provider codes (e.g. ECB, BLS, EUROSTAT, IMF, OECD) and their names. Use provider codes with list_datasets and get_series.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
_metaNo
nb_seriesNo
providersNoAvailable statistics providers
nb_datasetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and repeatability profile is fully covered upstream. The description adds useful content detail (a fixed catalog of 80+ providers with codes and names), but says nothing about freshness, caching, or size of the response. With annotations doing the heavy lifting, this is adequate but not rich.

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 sentences, both front-loaded with the essential information: what the tool returns and how to use the result. No filler, no restatement of the title, and the example codes make the output concrete in a few words.

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?

A zero-parameter, read-only catalog tool with full annotation coverage and a declared output schema needs little prose; the description covers scope, output shape, and downstream wiring. Nothing required for correct invocation 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description correctly avoids inventing inputs and instead explains what the output can be used for.

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 all statistics providers available in DBnomics'), quantifies the scope (80+), gives concrete example codes (ECB, BLS, EUROSTAT), and clarifies what the output contains (codes and names). An agent can immediately tell this is the catalog/discovery tool, apart from list_datasets and get_series.

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 second sentence explicitly routes usage: provider codes returned here are consumed by dbnomics_list_datasets and dbnomics_get_series, which establishes this as the upstream discovery step. It stops short of saying 'call this first when you don't know the provider code,' so it is clear context rather than a full when/when-not rule set.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.