Skip to main content
Glama
Sign In
DG-MCP

DG-MCP

by 0xNullAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

load_waveforms

Load .pulse waveform files or .zip archives containing .pulse files from a specified file path to configure device output patterns.

Instructions

从指定路径加载 .pulse 文件或包含 .pulse 的 .zip。

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": {
      "path": "<path>"
    },
    "name": "load_waveforms"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes绝对文件路径

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, description carries full burden but only states action and file types. Does not disclose read-only nature, potential side effects, or error behavior (e.g., invalid path).

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?

Single sentence with front-loaded action, no redundant words. Highly concise.

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?

Adequate for a simple one-parameter tool with no output schema, but lacks error context, file size limits, or relationship to sibling tools. Meets minimum viability.

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 already provides 100% coverage with description '绝对文件路径' (absolute file path). Description adds no extra meaning beyond the schema.

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

Purpose5/5

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

Description clearly states the verb (load) and resource (.pulse files or .zip containing .pulse) with specific file extensions. It distinguishes from siblings like list_waveforms which lists waveforms rather than loading them.

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 use this tool vs alternatives like list_waveforms or scan. Does not mention prerequisites (e.g., file existence) or post-load steps.

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