Skip to main content
Glama
mxcoppell

pixinsight

by mxcoppell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

inspect_environment

Report what a PixInsight installation provides—installed processes and scripts, Gaia and MARS data, XTerminator versions, and system resources—so agents can verify dependencies before processing.

Instructions

Report what this PixInsight installation has, by asking PixInsight. gaia: Gaia get-info for DR2, EDR3, DR3 and DR3/SP (valid, database files, magnitude range, mean spectra) and a 0.1-degree search on the lowest valid release. mars: one MultiscaleGradientCorrection run per MARS file (from PixInsight settings, or mars_files) on a temporary synthetic plate-solved image; per file: readable, missing or corrupt, and how many MARS reference images cover the probe position. xterminators: BlurXTerminator, NoiseXTerminator and StarXTerminator run once each on a temporary 64x64 image; reports version, ML model version and gpu/cpu from their console banner (null when not printed). processes: the PixInsight core version and build, whether MultiscaleAdaptiveStretch, MultiscaleGradientCorrection, BlurXTerminator, NoiseXTerminator and StarXTerminator are installed processes, and whether ImageSolver, AstrometricSolutionVerifier, DistortionEvaluator, FFTRegistration and MosaicByCoordinates are installed scripts, with the version each script declares; nothing is run. system: free and total memory, free space on the workspace volume. Temporary images are closed; open images are not touched. Without ra_deg/dec_deg the probe position is RA 0, Dec 0 and coverage is reported as null.

Input Schema

NameRequiredDescriptionDefault
ra_degNoProbe position right ascension, degrees [0, 360). Given with dec_deg.
dec_degNoProbe position declination, degrees [-90, 90]. Given with ra_deg.
sectionsNoSections to run (default: all)
mars_filesNoAbsolute .xmars paths to test instead of the configured ones

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.0
    • changedInput schema / properties / sections / items / enum
      Previous value: -[
-  "gaia",
-  "mars",
-  "xterminators",
-  "system"
-]New value: +[
+  "gaia",
+  "mars",
+  "xterminators",
+  "processes",
+  "system"
+]
  2. Addedv2.4.1

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that mars actually runs one MultiscaleGradientCorrection per file and xterminators actually runs BXT/NXT/SXT, that processes 'nothing is run', that temporary images are closed and open images are not touched, and that missing ra/dec yields a null coverage. These are non-obvious side effects that an agent must know before invoking.

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?

Front-loaded with the one-line purpose, and the gaia:/mars:/xterminators:/processes:/system: labels give useful internal structure. It is a dense wall of run-on text that would read better as a list, but every section clause conveys distinct, necessary 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?

With no output schema and no annotations, the description still specifies what each section reports (Gaia DB validity/range, per-file MARS status and coverage counts, terminator versions and gpu/cpu, installed processes/scripts with versions, memory and disk). Null behavior is called out, so an agent has what it needs to interpret results.

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?

Schema coverage is 100% so the baseline is 3, but the description adds real meaning beyond the schema: sections default to all, mars_files overrides configured paths, and the ra_deg/dec_deg pair defaults to RA 0/Dec 0 with null coverage. That edge-case behavior is not expressed in the schema.

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?

States a specific verb and resource – report what the PixInsight installation has – and enumerates exactly the five diagnostic sections (gaia, mars, xterminators, processes, system). This clearly separates it from siblings like list_processes, pixinsight_info, and workspace_info, since it aggregates environment capability checks rather than running on an image.

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 only implied: an agent can infer this is a pre-flight/environment-probe tool, but the description never says when to prefer it over list_processes, pixinsight_info, or workspace_info, nor any exclusions. Section labels describe content but do not route the agent among alternatives.

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

Deploy Server

Other Tools