Skip to main content
Glama

Export score

export_score

Make a file of one saved revision: a scoped, expiring download link and a resource link. Deliver it as a host attachment or through the panel's Download menu; never paste or rebuild download_url in chat. locked=true means this account has no download access for that format: offer the PDF.

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": {
      "score_id": "<score_id>",
      "revision": "<revision>"
    },
    "name": "export_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNopdf (follows the notation view), layout_pdf (staff), musicxml, mxl, mscz (MuseScore Studio), midi, mp3 or wav (the score played, not the recording), pages, parts, jianpu, jianpu_melody, jianpu_fixed, jianpu_voices, jianpu_fixed_voices, abc, mei, tab_text (plain-text TAB to show in chat), guitar_pro, watermarked_pdf, original_pdf, original_scores, original_midi, original_musicxml, provider_evidence, or editing_copy (the current MusicXML for your own edits to this score, once per round; not for the user).musicxml
part_idNoOne part only.
originalNo
revisionYesThe saved revision to export.
score_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / format / description
      Previous value: -"pdf (follows the notation view), layout_pdf (staff), musicxml, mxl, midi, mp3 or wav (the score played, not the recording), pages, parts, jianpu, jianpu_melody, jianpu_fixed, jianpu_voices, jianpu_fixed_voices, abc, mei, tab_text (plain-text TAB to show in chat), guitar_pro, watermarked_pdf, original_pdf, original_scores, original_midi, original_musicxml, provider_evidence, or editing_copy (the current MusicXML for your own edits to this score, once per round; not for the user)."New value: +"pdf (follows the notation view), layout_pdf (staff), musicxml, mxl, mscz (MuseScore Studio), midi, mp3 or wav (the score played, not the recording), pages, parts, jianpu, jianpu_melody, jianpu_fixed, jianpu_voices, jianpu_fixed_voices, abc, mei, tab_text (plain-text TAB to show in chat), guitar_pro, watermarked_pdf, original_pdf, original_scores, original_midi, original_musicxml, provider_evidence, or editing_copy (the current MusicXML for your own edits to this score, once per round; not for the user)."
  2. Changed9 schema fields changed
    • addedInput schema / properties / format / description
      Added value: +"pdf (follows the notation view), layout_pdf (staff), musicxml, mxl, midi, mp3 or wav (the score played, not the recording), pages, parts, jianpu, jianpu_melody, jianpu_fixed, jianpu_voices, jianpu_fixed_voices, abc, mei, tab_text (plain-text TAB to show in chat), guitar_pro, watermarked_pdf, original_pdf, original_scores, original_midi, original_musicxml, provider_evidence, or editing_copy (the current MusicXML for your own edits to this score, once per round; not for the user)."
    • removedInput schema / properties / original / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / original / default
      Removed value: -null
    • addedInput schema / properties / original / type
      Added value: +"string"
    • removedInput schema / properties / part_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / part_id / default
      Removed value: -null
    • addedInput schema / properties / part_id / description
      Added value: +"One part only."
    • addedInput schema / properties / part_id / type
      Added value: +"string"
    • addedInput schema / properties / revision / description
      Added value: +"The saved revision to export."
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already state that this is a write (readOnlyHint=false, destructiveHint=false, non-idempotent). The description still adds real behavior the annotations don't: the link is scoped and expiring, and locked=true signals that the account lacks download access for that format, so the PDF should be offered instead. It doesn't explain why the call is non-idempotent or what happens on repeat exports.

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?

Three sentences, front-loaded with the resource and the return values, then the delivery rules and the locked fallback. Every clause carries information, though the delivery rules and the locked=true note make it dense and slightly jargon-heavy.

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?

With no output schema, the description usefully names the returned artifacts (download link and resource link) and the locked=true outcome. It doesn't cover side effects such as quota use, link lifetime, or what happens on repeat exports of the same revision.

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 coverage is 60%. The description clarifies what revision means ('one saved revision') and ties format to the locked=true outcome, but part_id, original, and score_id get no explanation beyond the schema. This is enough to compensate only partly.

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 gives a specific verb and resource: it makes a file of one saved revision and returns a scoped, expiring download link plus a resource link. Scope ('one saved revision') separates it from list_score_versions and get_score, but no sibling is ever named, so routing still needs inference.

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

Usage Guidelines4/5

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

It clearly covers how to deliver the result (host attachment or the panel's Download menu) and forbids pasting or rebuilding download_url in chat, plus gives a fallback when locked=true. It never says when to prefer another tool, such as handing the user raw MusicXML via a different route.

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.

Resources