Skip to main content
Glama

Describe

audacity_describe
Read-onlyIdempotent

Retrieves the parameters for one Audacity 3.7.8 scripting command or effect from the bundled English catalogue, enabling valid audio-processing calls.

Instructions

Parameters of one scripting command or effect from the bundled English Audacity 3.7.8 catalogue.

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": {
      "command": "<command>"
    },
    "name": "audacity_describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYes

Output Schema

NameRequiredDescriptionDefault
idYes
tipNo
urlNo
nameYes
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: the data comes from a bundled, version-pinned (3.7.8), English-only catalogue, telling the agent results are static and may not reflect other languages or versions.

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 no filler, and the scoping qualifiers (bundled, English, 3.7.8) are packed in without burying the core meaning. It reads as a fragment rather than a sentence, but nothing is 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?

With one parameter and an existing output schema, little needs explaining about return values. However, the description omits the one thing an agent needs for correct sequencing in a complex 34-tool server: that this is the discovery step preceding command execution, and what it returns is documentation rather than results.

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 description coverage is 0%, but the single parameter is a fully enumerated list of 70+ names, and the description supplies the key missing meaning: the enum mixes effect names (Amplify, Reverb) with scripting commands (Select, GetInfo, Export2), so a caller knows both kinds are valid inputs.

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?

The description names a specific resource: the parameter metadata for a single scripting command or effect, and pins it to the bundled English Audacity 3.7.8 catalogue. That is clearly a read-only introspection call, distinguishable from execution siblings like audacity_command or audacity_effect, though it never names those alternatives outright.

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?

There is no explicit when-to-use statement, no mention that this should be called before audacity_command or audacity_effect to learn their arguments, and no when-not-to-use guidance. The introspection purpose is only inferable from the noun phrase.

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