Skip to main content
Glama

check_arrays

Inspects HDF5 array datasets for data quality issues, flagging NaN/Inf, dtype drift, fill values, and out-of-range values while summarizing per-dataset statistics.

Instructions

HDF5 / scientific-array EDA. Source must be loaded as hdf5 modality.

    Walks the h5py tree and aggregates leaf datasets by their leaf name (so
    all `.../energies` arrays across groups become one schema). Reports
    per-leaf shape examples, dtype consistency, finite/NaN/Inf %, range,
    units, valid_range. Flags NaN/Inf >1%, dtype drift across groups, fill
    values (~9.97e36 / ±9999), and out-of-range values vs declared valid_range.

    `max_groups` caps the walk depth for very large files. When the cap is
    hit, the result's `cap_hit=true` and a critical finding is surfaced —
    raise `max_groups` and re-run to cover the full file. Result also
    reports `n_groups_total` (true total) vs `n_groups_walked` (visited).
    Output size: scales with distinct leaf names; ~0.5–2KB per schema.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_idYes
max_groupsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly. It discloses aggregation logic, report details (shape, dtype, NaN/Inf %, range), flag thresholds (NaN/Inf >1%), fill values, cap_hit behavior, n_groups_total vs n_groups_walked, and output size scaling. This is exemplary behavioral transparency.

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 'HDF5 / scientific-array EDA' and follows a logical flow: context → mechanics → reports → edge cases → output size. Every sentence delivers meaningful information with no filler, making it appropriately sized for 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?

For a tool of this complexity with no annotations, the description covers the modality prerequisite, detailed operational behavior, edge case handling (cap), expected output content, and output size. Combined with the presence of an output schema, this is completely sufficient for an agent to select and invoke correctly.

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 provides only names and types (source_id required, max_groups integer default 10000). The description adds rich semantics for max_groups: caps walk depth, cap_hit triggers critical finding, and advises raising max_groups. source_id is not explicitly explained but is intuitive as a standard identifier. Given 0% schema coverage, this compensation is strong.

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 'HDF5 / scientific-array EDA' and details the action: 'Walks the h5py tree and aggregates leaf datasets by their leaf name.' This clearly identifies the tool's specific verb, resource, and scope, and distinguishes it from other check_* tools that focus on distributions, correlations, or quality.

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?

A clear prerequisite is stated: 'Source must be loaded as hdf5 modality.' It also explains when to adjust max_groups for large files. However, no explicit alternatives or when-not-to-use conditions are given, leaving some ambiguity among similar sibling tools.

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/charliecpeterson/edamcp'

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