Skip to main content
Glama

describe_catalogue_dataset

Inspect a published Syndex dataset's release: axes, spectra, emission lines, and citation info, without downloading the file. Verify coverage questions like metallicity ranges or available lines.

Instructions

Describe one published dataset in the Syndex catalogue.

Reports what a Syndex dataset's current release contains — for a grid, its axes and their extent, which spectra and emission lines it holds, the model it came from and how to cite it — without downloading the file. This is how to answer "does the published BPASS grid cover Z = 1e-5?" or "which lines would I get?" for a grid that is not installed here. Use inspect_local_grid for one that is.

Requires network access. Names come from search_catalogue.

Args: name: Catalogue dataset name, such as bpass-2-2-1-cloudy-sps-test. Not a filename and not a path.

Returns: On failure, a mapping with ok (False) and error, plus status when the catalogue rejected the name and hint when it could not be reached.

On success, a mapping with ``ok`` (``True``), ``source``,
``content_is_untrusted`` (always ``True``), the dataset's
``name``, ``display_name``, ``description``, ``data_type``,
``is_test``, ``is_recommended``, ``licence``, and
``current_release``. The release carries ``release_id``,
``published_at``, ``known_bug`` (with
``known_bug_description`` when set), the Synthesizer version
bounds, ``file`` (``filename``, ``format``, ``size_bytes``,
``sha256``), ``download_command``, ``citations``, and, for a
grid, ``grid`` with ``grid_type``, ``emission_type``, the model
and photoionisation code, the wavelength range, ``axes`` as
``{name, units, scale, count, minimum, maximum}``, ``spectra``,
and ``lines`` as ``{count, ids, truncated}``. Axis values
themselves are not returned; ``count``, ``minimum`` and
``maximum`` are what a coverage question needs.
``current_release`` is ``null`` for a dataset with nothing
published yet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses network dependency, failure modes with status/hint, success return structure, content_is_untrusted always being True, current_release being null for unpublished datasets, and the limitation that axis values are not returned. This is exemplary behavioral disclosure.

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 long, especially the Returns section, but it is well-structured with Args/Returns and front-loaded purpose and usage. Every sentence adds value; the length is justified by the richness of the return mapping and behavioral caveats, though a tighter summary of return fields could make it slightly more concise.

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 single parameter, the explicit network requirement, the detailed return contract, failure behavior, and clear differentiation from sibling tools, the description is complete enough for an agent to select and invoke the tool correctly without additional context.

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 coverage is 0%, but the description fully compensates: it explains the name is a catalogue dataset name, gives a concrete example, and explicitly says it is not a filename or path. It also tells the agent where names come from (search_catalogue), making the single parameter unambiguous.

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 it describes one published Syndex catalogue dataset, and enumerates exactly what information is reported: axes, spectra, lines, model, citation. It explicitly contrasts with inspect_local_grid, which handles installed grids, making sibling differentiation clear.

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?

It gives concrete example questions the tool answers, states network access is required, says names come from search_catalogue, and explicitly directs users to inspect_local_grid for local grids. This is strong when-to-use guidance with an explicit alternative.

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