Skip to main content
Glama

gdex-mcp

get_arco_variables

Return the list of ARCO variables available for a dataset.

Each row's type (index 2) is either "zarr" or "reference" (kerchunk).
A "reference" variable is often listed multiple times, once per kerchunk
reference variant (plain, "-remote-https", "-remote-osdf", etc.) — always
pick the "-osdf" variant's URL; the others' 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}) — that's better behaved than hand-building an
fsspec reference filesystem. A "zarr" row needs no variant picking — its
URL already routes through the OSDF director (rewritten automatically);
open it directly with xr.open_dataset(url, engine="zarr").

Results are capped at 300 rows (look for "truncated": true); narrow with
search_arco_variables if you hit the cap.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dsidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burdenhare. It discloses that zarr rows require no variant selection, that reference rows have multiple kerchunk variants, that the '-osdf' variant must be preferred, and that results can be truncated at 300 rows. These are critical non-obvious behaviors that an agent could not infer from the schema alone.

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 dense but every sentence earns its place. It front-loads the core purpose in the first sentence, then provides necessary technical guidance about variant selection, opening methods, truncation, and alternatives. There is no filler or repetition of schema information.

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?

For a tool with one parameter and an output schema, the description covers all operational concerns: row type semantics, variant selection, URL handling, opening recommendations, output truncation detection, and the sibling tool to use when narrowing results. Nothing an agent needs in order to call the tool correctly is missing.

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%, but the description compensates fully for the single parameter by giving the format 'dNNNNNN' and a concrete example 'd083002'. This is exactly the kind of semantic information an agent needs to construct a valid call, and it goes well beyond the bare schema definition of 'dsid'.

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 opens with a specific verb and resource: 'Return the list of ARCO variables available for a dataset.' It clearly distinguishes the tool from siblings like search_arco_variables by discussing exact row behavior and variant selection, so an agent knows what function this tool serves without opening the schema.

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 explicitly states when to use this tool versus the alternative by noting 'Results are capped at 300 rows... narrow with search_arco_variables if you hit the cap.' This gives an agent a concrete decision rule for choosing between the two related tools. It also provides context for opening the returned URLs, which informs downstream usage.

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.