PXE200 SA MCP

Overview Schema Source Related Servers Discussions Admin

Report Export

report_export

Generate and export test report documents from the active spectrum-analyzer session, with HTML, DOCX, or both output formats.

Instructions

Generate the report document(s) from the active session.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "report_export"
  }
}

Input Schema

Name	Required	Description	Default
`fmt`	No	html \| docx \| both	both

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

B3.2/5.0

Behavior2/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 implies a side-effecting write (documents are produced) but says nothing about where files are written, whether existing exports are overwritten, whether an active report is required, or any auth/permission needs.

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?

A single, front-loaded sentence with the verb and resource first and no filler. The trailing phrase 'from the active session' is vague, but no words are wasted.

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 return values need not be explained, and there is only one well-documented parameter. Still, for a side-effecting export tool with zero annotation coverage, the description should mention the output destination/overwrite behavior and the prerequisite session state.

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% and the single 'fmt' parameter already documents its html|docx|both values. The description's plural 'document(s)' faintly hints that multiple formats can be produced, but adds no real meaning beyond the schema; baseline 3 applies.

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 ('Generate') and resource ('report document(s)'), so the agent knows this produces output artifacts rather than editing or reading report state. However, it offers no differentiation from siblings like report_start or report_open, which could plausibly also be described as 'generating' a report.

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?

'from the active session' implies a precondition (a session must already exist and hold report content), which is a weak usage signal. There is no explicit when-to-use vs. report_start/report_open/report_status guidance and no stated exclusions.

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