Skip to main content
Glama

save_upload

Free. Step 2: register the uploaded file as a song in the user's library. Returns a song id usable by re-creation and processing tools.

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": {
      "key": "<key>"
    },
    "name": "save_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYeskey returned by upload_audio.
nameNoSong title (e.g. the file name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations carry only destructiveHint=false, so the description adds real value: it discloses the cost ('Free'), the pipeline position, and the return contract (a song id usable by re-creation and processing tools). It does not explain idempotency, what happens on duplicate keys, or whether a library entry can be undone, which keeps it from 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?

Two short sentences, front-loaded with the cost signal and the step ordering, with no filler. The return-value clause earns its place by telling the agent what it gets back.

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 two-parameter tool with no output schema, the description covers cost, ordering, and the shape of the return value, which is enough for correct invocation. Minor gaps are failure behavior and duplicate-key handling, but nothing essential to calling it is missing.

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 description coverage is 100%, with both 'key' and 'name' documented including the upload_audio source and a title example. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline 3 applies.

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 concrete verb and resource: 'register the uploaded file as a song in the user's library', and labels itself 'Step 2' of an upload pipeline, which implicitly separates it from the earlier upload_audio step. It stops short of naming upload_audio or any sibling explicitly in the description text, so differentiation relies partly on the schema's 'key returned by upload_audio' note.

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

Usage Guidelines3/5

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

'Step 2' conveys ordering (upload must happen first) and the schema confirms the prerequisite, so usage is implied rather than stated. There is no explicit when-not guidance and no mention of related alternatives such as add_instrumental or add_vocals, which an agent might confuse with post-upload registration.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.