Skip to main content
Glama
mxcoppell

pixinsight

by mxcoppell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

run_bxt

Run BlurXTerminator on a view to sharpen stellar and non-stellar details or apply PSF correction without sharpening.

Instructions

Run BlurXTerminator on a view. correct_only applies PSF correction without sharpening; otherwise sharpen_nonstellar and sharpen_stellar (the process's sharpen_stars parameter) control sharpening strength. ml_version is the process's neural network model version; omitted, the process keeps its own setting.

Input Schema

NameRequiredDescriptionDefault
view_idYesView ID to process
ml_versionNoNeural network model version (the process's ml_version parameter)
correct_onlyNoCorrect-only mode: PSF correction with no sharpening
sharpen_stellarNoStellar sharpening, 0 to 1 (default 0.50)
adjust_star_halosNoStar halo adjustment, -1 to 1 (default 0.0)
sharpen_nonstellarNoNon-stellar sharpening, 0 to 1 (default 0.50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.0
    • addedInput schema / properties / ml_version
      Added value: +{
+  "description": "Neural network model version (the process's ml_version parameter)",
+  "type": "number"
+}
  2. First observedv2.1.0

TDQS

B3.3/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 burden, and it does disclose real behavior: correct_only disables sharpening, the two sharpen params control strength, and omitting ml_version leaves the process's own setting intact. However, it says nothing about whether the view is modified in place, whether the operation is reversible, or expected runtime.

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?

Three tight sentences, front-loaded with the primary action, then mode semantics. No filler, though the sentence structure packs two distinct behaviors into one line.

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 6-parameter image-mutating process with no annotations and no output schema, the description covers the core mode/version semantics but omits the mutation profile (in-place edit, undo, masking) and ignores adjust_star_halos entirely, leaving a real gap.

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 already 100%, so the baseline is 3, but the description adds genuine meaning: it maps correct_only and sharpen_nonstellar/sharpen_stellar onto the underlying process's sharpen_stars parameter and explains that omitting ml_version preserves the existing process setting, which the schema does not state.

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?

States a specific verb and resource ('Run BlurXTerminator on a view'), which is distinct from siblings like run_nxt, run_sxt and run_pjsr. It does not explicitly differentiate itself from those related process runners, but the named process makes the purpose unambiguous.

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

Usage Guidelines2/5

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

No guidance on when to choose BXT over its siblings (run_nxt, run_sxt) or what preconditions exist (e.g. linear vs stretched data, need for a mask). The mode explanation concerns parameter behavior rather than tool selection, so the agent gets no routing help.

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