Galaxy Cluster Catalogs MCP Server

plot_completeness

Visualize survey completeness and selection functions for Planck, ACT DR6, and SPT-SZ cluster catalogs, producing heatmaps, histograms, or bar charts based on the selected dataset.

Instructions

Plot the survey completeness / selection function.

Planck: heatmap of completeness C(Y500, theta500) at a chosen SNR cut.
ACT DR6: histogram of tile y0 RMS noise levels.
SPT-SZ: bar chart of field areas and noise correction factors.

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": {
      "output_dir": "<output_dir>"
    },
    "name": "plot_completeness"
  }
}

Input Schema

Name	Required	Description	Default
`dataset`	No	Dataset key: psz2, act_dr6, or spt_sz.	psz2
`snr_cut`	No	SNR threshold for the completeness contour (Planck only).
`variant`	No	Planck variant (default MMF3_cosmology).
`output_dir`	Yes	Directory for the PNG.

Output Schema

Name	Required	Description	Default
`files`	Yes
`status`	Yes
`message`	Yes
`metadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does useful work by disclosing the distinct output content per dataset, but it never states that the tool writes a PNG file into output_dir, whether existing files are overwritten, or what runtime/data access is needed to build the Planck heatmap. For a no-annotation tool that emits files, that is a meaningful gap.

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?

A single front-loaded purpose sentence followed by three tight per-dataset bullets, with no filler or repetition. Every line adds distinct information about what the output looks like.

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?

With an output schema present, return values need not be explained, and the per-dataset breakdown covers the main behavioral surface for a 4-parameter plotting tool. Minor omissions: the 'variant' parameter goes unmentioned and the file-writing side effect of output_dir is never stated.

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 the schema already documents dataset keys, the SNR cut, and output_dir; baseline is 3. The description adds only a little: it implicitly ties the SNR cut to the Planck completeness contour and maps datasets to plot types, but it never mentions the 'variant' parameter at all.

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?

Specific verb+resource: 'Plot the survey completeness / selection function', followed by concrete per-dataset outputs (Planck heatmap of C(Y500, theta500), ACT DR6 y0 RMS histogram, SPT-SZ field-area bar chart). An agent knows exactly what artifact each call produces. It never contrasts itself with plotting siblings like plot_mass_redshift or plot_counts_vs_prediction, so sibling differentiation is left to the reader.

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 through the dataset menu: pick 'psz2' for SNR completeness, 'act_dr6' for noise histograms, 'spt_sz' for field areas, which helps an agent choose a dataset. But there is no explicit when-to-use vs alternatives guidance, and no pointer to fetch_cluster_selection_function for agents that want the underlying numbers rather than a plot.

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