Skip to main content
Glama

convert_astronomy

Convert FITS astronomy files to JSON or CSV, extracting headers and selected HDU data for analysis. Requires astropy for full FITS data extraction.

Instructions

Convert astronomy data formats: FITS→JSON (header extraction). For full FITS data extraction, requires astropy.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_astronomy"
  }
}

Input Schema

NameRequiredDescriptionDefault
hduNoHeader Data Unit index (optional, default 0)
inputPathYesAbsolute path to input astronomy file
outputPathYesAbsolute path for output file (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add real behavioral context by clarifying that the default path only performs header extraction and that full FITS data requires the astropy dependency, which an agent would otherwise not know. It stops short of covering write semantics for outputPath (overwrite behavior), what happens when astropy is absent, or what the extracted output structure looks like.

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?

Two short, front-loaded sentences with no filler, and the capability caveat is placed immediately after the primary action. It is efficient, though the space saved is partly spent on a narrower format claim than the schema supports.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter conversion tool with no annotations and no output schema, the definition covers the core action and the astropy dependency caveat but leaves the agent guessing on output content, CSV output support, and overwrite behavior at outputPath. Adequate but with clear gaps relative to the tool's surface area.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all five parameters are already documented, establishing a baseline of 3. The description adds only marginal meaning beyond the schema: it confirms FITS input handling and header-only extraction, but never explains the 'hdu' index parameter or clarifies the relationship between the enum format values and the tool's stated FITS→JSON focus.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Convert astronomy data formats') and states the primary direction ('FITS→JSON (header extraction)'), which is enough to distinguish it from siblings like convert_image or convert_geoscience. However, it only describes the FITS→JSON path while the schema permits outputFormat 'csv', so the stated purpose covers a narrower surface than the tool actually supports.

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

Usage Guidelines3/5

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

Usage is implied by the domain (astronomy/FITS files) and the note that full data extraction 'requires astropy' hints at a capability boundary. But there is no explicit when-to-use statement, no guidance on choosing between output formats, and no mention of when a sibling converter would be the better pick.

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