Skip to main content
Glama

Dbnomics Search

dbnomics_search
Read-onlyIdempotent

Full-text search across all providers. Returns matching series with provider/dataset/series codes and human labels.

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": {
      "query": "unemployment rate"
    },
    "name": "dbnomics_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults, 1-1000 (default 20)
queryYesFree-text search
offsetNo0-based offset

Output Schema

NameRequiredDescriptionDefault
_metaNo
resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the shape of results (provider/dataset/series codes plus human labels), but says nothing about ranking, result ordering, or pagination behavior for a 1-1000 limit range.

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?

Two short sentences with the core action front-loaded and no filler. Efficient, though the second sentence partly duplicates what the output schema and parameter names already convey.

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?

With an output schema present and full schema description coverage, the description need not document return structures or parameter details. For a three-parameter read-only search tool it is essentially complete, with only minor gaps around ranking and result ordering.

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

Parameters3/5

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

Schema coverage is 100% and every parameter (query, limit, offset) already carries its own description, so the description contributes no additional parameter semantics such as query syntax, matching rules, or how offset interacts with limit. The baseline of 3 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?

The description states a specific verb and resource: 'Full-text search across all providers' returning 'matching series' with codes and labels. That is clearly distinguishable from series-fetching siblings, though it never names an alternative such as a within-dataset search, so sibling differentiation 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?

The phrase 'across all providers' implies this is the broad/discovery search, contrasting implicitly with narrower scope search tools, but there is no explicit when-to-use or when-not-to-use statement and no alternative is named.

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.