Skip to main content
Glama
nescoffee-create

SDMX MCP Gateway

probe_data_url

Check whether an SDMX data query returns observations using a lightweight probe that fetches just one record to verify data availability.

Instructions

Probe an exact SDMX data query and return whether it contains data.

This answers the question that validation and code-usage checks cannot:
does this exact query return observations right now?

Accepts either a complete data URL or structured parameters.
Uses lightweight probing (firstNObservations=1) to minimise payload.

Args:
    data_url: Complete SDMX data URL to probe
    dataflow_id: Dataflow ID (alternative to data_url)
    filters: Dimension filters (alternative to data_url)
    start_period: Start time period
    end_period: End time period
    agency_id: Owning agency when different from the session default.
        Required for OECD sub-agency flows (e.g. pass "OECD.STI.STP"
        alongside dataflow_id="DSD_RDS_GERD@DF_GERD_SOF"). Only consulted
        when data_url is not provided; ignored when data_url is.
    sample_observations_limit: Max sample observations to return
    max_distinct_values_per_dimension: Max distinct values per dimension summary
    timeout_ms: Probe timeout in milliseconds
    endpoint: Optional endpoint key (e.g. "FBOS", "ECB") to target a
        specific provider for this call only. Defaults to the session's
        current endpoint.

Returns:
    Probe result with status, observation count, shape, and sample data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersNo
data_urlNo
endpointNo
agency_idNo
end_periodNo
timeout_msNo
dataflow_idNo
start_periodNo
sample_observations_limitNo
max_distinct_values_per_dimensionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoDiagnostic notes
statusYesProbe outcome: 'nonempty' if observations were returned, 'empty' if the query resolved to zero observations, 'error' if the probe failed (HTTP error, parse failure, etc.)
dimensionsNoSummary of observed dimension values
series_countNoNumber of distinct series
geo_dimension_idNoGeography dimension ID if detected
observation_countNoNumber of actual observations returned
query_fingerprintNoSHA-256 fingerprint of the normalised query
time_period_countNoNumber of distinct time period values
has_time_dimensionNoWhether a time dimension was detected
sample_observationsNoBounded sample of observations
Behavior5/5

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

With no annotations provided, the description fully carries the transparency burden. It discloses key behaviors: uses 'lightweight probing (firstNObservations=1)' to minimize payload, returns 'status, observation count, shape, and sample data', and clarifies that agency_id is 'Required for OECD sub-agency flows' and 'ignored when data_url is'. This gives the agent concrete expectations about side effects and output.

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?

The description is well-structured with a clear intro, use-case statement, parameter list, and return description. It is somewhat verbose due to the detailed parameter explanations, but every sentence adds necessary context. It could be slightly tightened, but overall it earns its length given the tool's complexity.

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?

Given the 10-parameter complexity and the presence of an output schema, the description is complete. It explains input alternatives, output structure, timeout defaults, endpoint selection, and special cases like sub-agency flows. The agent has all context needed to invoke the tool correctly without needing to infer from structured data.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It does so admirably, explaining all 10 parameters with relationships, examples, and edge cases. For instance, it notes data_url and dataflow_id are alternatives, clarifies agency_id usage conditions, and provides endpoint examples. This adds significant meaning beyond the raw 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?

The description clearly states the tool 'Probe an exact SDMX data query and return whether it contains data', using a specific verb and resource. It explicitly distinguishes from sibling tools by explaining it answers the question validation and code-usage checks cannot, making its unique purpose unambiguous.

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 description provides clear context on when to use the tool: 'This answers the question that validation and code-usage checks cannot'. It also explains the flexible input modes (data_url or structured parameters). However, it does not explicitly name alternative sibling tools or state when not to use it, though the comparison to validation/code-usage checks implies it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nescoffee-create/sdmx-mcp-gateway'

If you have feedback or need assistance with the MCP directory API, please join our Discord server