gdex-mcp

has_arco

Check whether Analysis-Ready Cloud-Optimized (ARCO) data is available for a dataset.

For analysis tasks, call this (and check for a "Kerchunk Reference Files"
group via get_file_groups) before reaching for raw data files — reading
through ARCO/kerchunk references avoids downloading whole files just to
subset them. When picking among kerchunk reference variants, always use
the one with "-osdf" in its name (see get_arco_variables) — other
variants' chunk targets can be internal paths that only resolve on
NCAR's network. Open it with xr.open_dataset(url, engine="kerchunk",
storage_options={"remote_protocol": "https", "lazy": True}) rather than
hand-building an fsspec reference filesystem.

Args:
    dsid: Dataset ID (dNNNNNN), e.g. d083002

Input Schema

TableJSON Schema

Name	Required	Description	Default
`dsid`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers meaningful behavioral context: it warns about internal-path chunk targets in non-OSDF variants and specifies the exact xr.open_dataset invocation. It doesn't discuss edge cases like empty results, but the output schema likely covers return structure.

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?

The description is front-loaded with the core purpose and then efficiently delivers usage guidance, a critical warning, and parameter format. Every sentence earns its place, and the extra length is justified by the need to prevent a likely kerchunk misuse.

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 a single parameter, an output schema, and clear operational instructions, the description is complete: it says when to use the tool, which sibling tools to call, how to open the data, and what dsid format to provide. Nothing essential 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 schema only defines dsid as a string, so the description's addition of the format '(dNNNNNN)' and the concrete example 'd083002' is valuable. For a single parameter, this is sufficient practical semantic guidance.

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 states a specific action and resource: 'Check whether Analysis-Ready Cloud-Optimized (ARCO) data is available for a dataset.' It also distinguishes the tool from sibling tools by framing it as a pre-check before raw data access, which helps an agent select it correctly.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: call this before reaching for raw data files for analysis tasks. It also names sibling tools (get_file_groups, get_arco_variables) and instructs the agent on which variant to use, making the routing decision clear.

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

All gdex-mcp tools Inspect

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.