Skip to main content
Glama

pitch_correction

Read or set whether playback speed preserves original pitch, keeping sped-up speech natural; disable it when intentional pitch shifts are needed.

Instructions

Read or set whether changing playback speed keeps the original pitch. On by default, which is what makes 1.5x speech listenable rather than chipmunk-like. Turn it off only when the pitch shift is the point, such as checking a musical tempo change.

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

Input Schema

NameRequiredDescriptionDefault
enabledNoOmit to read the current setting

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does most of it: it reveals the default value, the practical effect of each state, and the intent behind toggling off. It does not say whether the setting is global or per-item, or whether a change applies to in-flight playback, which keeps it short of a 5.

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?

The read/set framing and the default are front-loaded, and each sentence adds something. The chipmunk analogy is flavor rather than specification, so a small amount of text is not strictly load-bearing.

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

Completeness4/5

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

For a single optional boolean with no output schema and no annotations, the definition covers purpose, default, effect, and the reason to disable. The only real omission is scope (global versus per-file/session) and whether the change is immediate, which an agent might want before calling.

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

Parameters4/5

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

Schema coverage is 100% and the schema already says 'Omit to read the current setting', so the baseline is a 3. The description earns above baseline by explaining what the boolean actually controls (pitch preservation during speed changes) and why the default is on, which gives the value real meaning rather than just a flag.

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?

The description opens with a specific verb pair and resource: 'Read or set whether changing playback speed keeps the original pitch.' That names the exact setting being manipulated and makes the dual read/write nature obvious, which the terse tool name alone would not.

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

Usage Guidelines5/5

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

It states the default ('On by default') and gives an explicit exclusion rule for the non-default case: 'Turn it off only when the pitch shift is the point, such as checking a musical tempo change.' That is a when-to-use and a when-not-to-use in one, with a concrete example.

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