PXE200 SA MCP

Overview Schema Source Related Servers Discussions Admin

Report Start

report_start

Start a new report session to collect screenshots, traces, and measurements in one folder; pass the DUT's rated power for +-3 dB result checks.

Instructions

Start a new report session. Later screenshots / traces / measurements are saved into its folder. Pass rated_power_w whenever the DUT's power rating is known.

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": {
      "title": "<title>"
    },
    "name": "report_start"
  }
}

Input Schema

Name	Required	Description
`dut`	No	Device under test / settings
`setup`	No	Test setup, e.g. 'TX -> 40 dB attenuator -> PXE200'
`title`	Yes
`project`	No
`engineer`	No
`description`	No
`rated_power_w`	No	DUT rated output power in W. Every power result is checked against it (+-3 dB) and flagged.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

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 behavioral burden. It discloses that this starts a new report session whose folder receives later artifacts, and that rated_power_w triggers power-result checks. However, it does not describe permissions, whether a prior session is affected, or what happens if a report already exists.

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?

Two short sentences are front-loaded with the core action and lifecycle effect. There is no wasted text, and the rated_power_w guidance is placed immediately after the main purpose.

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?

An output schema exists, so the description need not explain return values. It still leaves gaps for a 7-parameter creation tool: most parameter meanings are undocumented, and prerequisites such as whether a report must be closed first are absent. It is adequate but not complete.

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 coverage is only 43% across 7 parameters. The description mentions rated_power_w and gives a usage condition for it, but it does not explain the required title or the purpose of project, engineer, description, and other fields that lack schema descriptions.

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: 'Start a new report session.' It clearly implies creation of a new report rather than opening an existing one, though it does not explicitly name report_open or other siblings as alternatives.

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?

The description gives implied usage guidance by saying later screenshots, traces, and measurements are saved into the session folder, which tells the agent to start the report before capturing artifacts. It also gives a conditional usage note for rated_power_w, but it does not state when not to use this tool or explicitly compare it with report_open/report_list.

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