Skip to main content
Glama

import_audio

Copies an authorized local music or voice track to a new location while recording its license provenance.

Instructions

Copy a local authorized music/voice track with license provenance.

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": {
      "input": "<input>",
      "output": "<output>",
      "license": "<license>"
    },
    "name": "import_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes
licenseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false, idempotentHint=false). The description adds 'local' (consistent with openWorldHint=false) and the requirement for license provenance, which is real context beyond the schema. It does not disclose what happens if the license is invalid, whether an existing output file is overwritten, or how the copy is performed, so it is useful but incomplete.

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 compact sentence with the key qualifiers front-loaded and no filler. Its brevity is efficient, though it borders on under-specified rather than merely concise.

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

Completeness2/5

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

The tool writes data (non-read-only, non-destructive) with three undocumented parameters and an output schema that excuses return-value explanation. Even so, the description omits input/output format, license validation behavior, and overwrite semantics, leaving significant gaps for a mutation tool.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It loosely maps input to a 'music/voice track', output to the copy destination, and license to 'license provenance', but never states whether input/output are file paths, URLs, or asset IDs, nor what a valid license string looks like (the schema only bounds it at 5-2000 chars).

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 and resource: 'Copy a local authorized music/voice track.' The qualifiers 'local', 'authorized', and 'license provenance' narrow it meaningfully against siblings like mix_audio or generate_voiceover, though no sibling is named 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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The word 'local' and 'authorized' imply preconditions, but an agent gets no instruction on when to pick import_audio over generate_voiceover or inspect_media_assets.

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