Skip to main content
Glama
Sign In
WaveMind Preset MCP

WaveMind Preset MCP

by Hemir95
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Read Preset

read_preset

Retrieve a NAM Universal II preset's slot file paths and key parameters to inspect, back up, or recreate its configuration.

Instructions

Read a preset: slot file paths and key parameters.

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": {
      "nombre": "<nombre>"
    },
    "name": "read_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nombreYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/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 burden. 'Read' strongly implies a safe, non-mutating operation and the mention of returned content adds useful context, but it says nothing about error behavior when the preset is missing or whether any auth is required. An output schema exists, so return structure need not be explained here.

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 tight sentence with the action front-loaded and zero filler. It is efficient, though bordering on under-specified for a tool with an undocumented parameter.

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?

The output schema covers return values, so the description needn't explain them. However, with a required parameter left undefined and no usage or failure context, the definition is only minimally complete for correct invocation.

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?

The single parameter 'nombre' has 0% schema description coverage, so the description must compensate — and it does not. It never clarifies whether 'nombre' is a preset name, slot identifier, or file path, leaving the one required input effectively undocumented.

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+resource ('Read a preset') and adds what is returned ('slot file paths and key parameters'). This distinguishes it from list_presets and the create/delete siblings, though it never names those alternatives explicitly.

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 when-to-use guidance and no alternatives named. An agent must infer that this is the singular counterpart to list_presets, with nothing in the text confirming that or describing prerequisites such as needing an existing preset name.

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