teardown-observe

Overview Schema Source Related Servers Discussions Admin

probe_cli

Sweep CLI feature inputs, run pairwise option combinations, and calibrate environment noise to generate a probe table with mined decision-table claims and unknowns.

Instructions

Probe a CLI feature: one-factor sweep, pairwise over accepted classes, noise calibration (rerun + env variations), probe table, mined decision-table claims and unknowns. hints = {cmd, base, selector_options, takes_files, default_input, sweep_inputs, inputs, pair_inputs, operand_type, unicode_argv, skip_options, extra_inputs, extra_values}.

Input Schema

Name	Required	Description	Default
`hints`	Yes
`feature`	Yes
`pairwise`	No
`env_sample`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

C2.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the internal process (sweeps, pairwise combinations, noise calibration via rerun and env variations), but it does not state whether CLI commands are executed, what side effects or permissions are involved, or any safety constraints. The output schema covers return values, so that gap is less serious.

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 front-loaded with the tool's purpose and then enumerates key processes. It is dense but not wasteful, and the hints key list, while long, is necessary to partially compensate for the schema's lack of descriptions.

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

Completeness2/5

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

This is a complex probing tool with a nested hints object and no annotations. While an output schema exists, the description leaves too much unspecified about parameter semantics, execution behavior, and safety for an agent to invoke it confidently without inspecting the implementation.

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

Parameters2/5

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

Schema description coverage is 0%, and there are four parameters including a nested hints object with many keys. The description lists the hints keys, which is helpful, but provides no meaning, type, constraints, or examples for any of them, and top-level parameters like feature, pairwise, and env_sample are only obliquely referenced.

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 states a specific verb and resource: probing a CLI feature. It enumerates the probing modes (one-factor sweep, pairwise, noise calibration, probe table, mined claims/unknowns), so the purpose is clear, but it does not explicitly distinguish this tool from siblings like discover_cli or suggest_probes.

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?

There is no explicit guidance on when to use this tool versus alternatives such as suggest_probes, discover_cli, or probe_web_field. The only usage signal is the implied context of probing a CLI feature, with no stated prerequisites or exclusions.

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