Skip to main content
Glama

DatoQA

by dev.workers.bhazarstudio.datoqa
OverviewDiscussionsAdmin

get_us_economic_indicators

Read-onlyIdempotent

BLS US monthly consumer_price_index (CPI-U NSA, 1982-84=100), unemployment (SA percent civilian labor force 16+), nonfarm_employment (SA thousands of payroll jobs). Default last 12 monthly periods; limit 1-120 or exact period YYYY-MM, mutually exclusive. Retains source decimals, missing values, preliminary/revision footnotes and evidence. Not real-time, a percent inflation rate or monthly job creation; not independently verified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoLatest monthly periods, default 12; omit when period is supplied.
periodNoExact source month YYYY-MM, for example 2025-06; cannot be combined with limit.
indicatorYesBLS monthly series key; use list_us_economic_indicators to check availability and units.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
noticeNo
statusYesRead this before using values; a successful transport does not establish data availability.
returnedYesDomain-specific result count, not necessarily the number of stored records in items.
directoryNo
available_periodNo
independently_verifiedNoOfficial-source checks are not independent factual corroboration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / provenance / properties / verification_level / enum
      Previous value: -[
-  "official_source_and_schema_checked",
-  "method_specific"
-]New value: +[
+  "official_source_and_schema_checked",
+  "public_aggregator_and_schema_checked",
+  "method_specific"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description layers on substantive data-quality behavior: it retains source decimals, missing values, and preliminary/revision footnotes, and it is explicitly not real-time and not independently verified. That staleness and revision-caveat disclosure is exactly the context an agent needs before citing these numbers.

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?

Front-loaded with the resource and series definitions, then defaults, then caveats; the final 'Not real-time, ... not independently verified' clause is slightly compressed and reads as a dash-list. Dense but nearly every clause earns its place.

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?

With an output schema present, return-value explanation is unnecessary, and the description still supplies the defaults, the limit/period interaction, series semantics, and revision/staleness caveats. Nothing material is missing for correct invocation or interpretation.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds meaning the enum keys alone do not carry: what each indicator actually measures, its units and index base, plus the default and mutual-exclusivity of limit/period. This is genuine semantic value beyond the schema.

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+resource (US monthly BLS indicators) and enumerates the three exact series with their units and seasonal-adjustment basis (CPI-U NSA 1982-84=100, unemployment SA percent, nonfarm_employment SA thousands). An agent can distinguish this from list_us_economic_indicators and get_economic_indicators without opening a schema.

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?

Explicitly gives the default (last 12 monthly periods) and the mutually-exclusive selection modes (limit 1-120 vs exact period YYYY-MM), plus negative scoping: 'Not real-time, a percent inflation rate or monthly job creation.' It does not name a sibling alternative for availability checks in the description text (that cue lives in the schema), so it stops just short of 5.

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

All DatoQA 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