Skip to main content
Glama

Dbnomics

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search

search
Read-onlyIdempotent

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

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results requested
offsetNoOffset of results
seriesNoList of matching time series
total_countNoTotal matching series count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "unemployment rate"
+  },
+  {
+    "limit": 50,
+    "query": "GDP France"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "limit": {
+      "description": "Number of results requested",
+      "type": "number"
+    },
+    "offset": {
+      "description": "Offset of results",
+      "type": "number"
+    },
+    "series": {
+      "description": "List of matching time series",
+      "items": {
+        "properties": {
+          "dataset_code": {
+            "description": "Dataset identifier",
+            "type": "string"
+          },
+          "provider_code": {
+            "description": "Provider identifier",
+            "type": "string"
+          },
+          "series_code": {
+            "description": "Series identifier",
+            "type": "string"
+          },
+          "series_name": {
+            "description": "Human-readable series name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_count": {
+      "description": "Total matching series count",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already indicate safe, read-only, idempotent behavior. Description adds context about searching across all providers and return format, but no additional behavioral traits beyond what annotations convey.

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?

Description is a single concise sentence that conveys the core purpose. Could be slightly more structured but is efficient.

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 low complexity, full schema coverage, and output schema present, the description sufficiently covers what the tool does and returns.

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% with clear parameter descriptions. The tool description adds no new meaning beyond the schema.

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?

Description clearly states it performs full-text search across all providers and returns series with codes and labels. However, it does not differentiate from sibling tools like 'search_within' or 'find_series'.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. Sibling tools exist but no mention of their distinctions.

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

All Dbnomics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources