Skip to main content
Glama
Sign In
Instrument MCP Server

Instrument MCP Server

by zeng-andrew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mxa_set_harm_average

Set harmonic average on an MXA signal analyzer by specifying alias and parameters in JSON, using SCPI commands for automation.

Instructions

[MXA] 设置谐波平均

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": "mxa_set_harm_average"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasNodefault
params_jsonNo{}

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

Description provides no behavioral traits beyond the annotation's destructiveHint=false. Does not explain if it writes settings, triggers actions, or returns data. With minimal annotations, the description should compensate but fails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely short, but underspecified rather than concise. Lacks necessary detail for effective use.

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

Completeness1/5

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

Given the tool's complexity (optional parameters, existence of many sibling tools), the description is completely inadequate. Does not explain purpose, parameters, or output, leaving the agent with no actionable information.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the parameters 'alias' or 'params_json'. No guidance on format, allowed values, or typical usage for params_json.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'set harmonic average' but is vague; does not specify what aspect of harmonic average is being set. Sibling tools like 'mxa_set_average_type' and 'mxa_set_harm_average_count' suggest more specific meanings, but this description lacks differentiation.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus alternatives like 'mxa_set_harm_average_count' or 'mxa_set_averaging'. No context or prerequisites mentioned.

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