Skip to main content
Glama

gdex-mcp

search_arco_variables

Search ARCO variables by name for a dataset.

As with get_arco_variables, a "reference" (kerchunk) match is often
listed once per variant — always pick the "-osdf" variant's URL (reachable
from anywhere), and open it with xr.open_dataset(url, engine="kerchunk",
storage_options={"remote_protocol": "https", "lazy": True}). A "zarr"
match needs no variant picking — its URL already routes through the OSDF
director (rewritten automatically); open it directly with
xr.open_dataset(url, engine="zarr").

Args:
    dsid: Dataset ID (dNNNNNN), e.g. d083002
    query: Search text to match against variable names

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dsidYes
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the kerchunk vs zarr distinction and precisely instructs how to handle the '-osdf' variant and open datasets with xr.open_dataset. This adds significant value beyond a simple search description, though it does not cover every output nuance.

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 structure is efficient: one-sentence purpose up front, followed by necessary variant-handling behavior and a concise Args section. The longer variant guidance is dense but directly actionable, and no sentence is filler.

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?

The description covers purpose, parameters, and the important variant-picking behavior, while the output schema handles return structure. It does not specify matching semantics (substring vs exact, case sensitivity) or explicitly contrast with get_arco_variables, but it is sufficient for correct invocation.

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 document both parameters. It does exactly that: dsid is specified as a dNNNNNN ID with an example (d083002), and query is explained as search text matched against variable names. This fully compensates for the schema's lack of descriptions.

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-resource-scope statement: 'Search ARCO variables by name for a dataset.' This clearly distinguishes it from sibling get_arco_variables, especially since it immediately references that tool while focusing on name-based search.

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?

It states the search-by-name use case clearly, so an agent can infer when to invoke it. It references get_arco_variables as context but does not explicitly say when to prefer this tool over that one or list exclusions, so it stops short of full explicit guidance.

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.