Skip to main content
Glama

ScoreStarling

by com.scorestarling
OverviewDiscussionsAdmin

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.

Input Schema

NameRequiredDescriptionDefault
formatNopdf (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).musicxml
part_idNoOne part only.
originalNo
revisionYesThe saved revision to export.
score_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With annotations already declaring readOnlyHint=false, destructiveHint=false, and idempotentHint=false, the description usefully adds that the link is scoped and expiring, names the resource link, and specifies delivery constraints. It also discloses the access restriction represented by locked=true. It does not clarify whether repeated calls create new links or describe other side effects, but it adds meaningful behavior beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, followed by delivery rules and the locked-format fallback. Every sentence carries operational value, and there is no redundant restatement of the name or title.

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 5-parameter export tool with no output schema, the description explains the key return artifacts: a scoped expiring download link and a resource link. Annotations cover the safety profile, and the locked=true fallback is included. It still leaves some schema-level parameters such as original and part_id underexplained, so it is strong but not fully complete.

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%, and the description adds meaning mainly for revision ('one saved revision') and for format in the locked=true fallback. The schema itself already exhaustively documents format, while score_id and original have no description and part_id has only 'One part only.' in the schema. The description does not compensate enough for the remaining parameter ambiguity.

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 uses a specific verb and resource: 'Make a file of one saved revision,' and immediately names the two outputs, a scoped download link and a resource link. This clearly distinguishes export from sibling read/list/get tools such as get_score, list_scores, and read_score_panel.

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 gives clear delivery guidance ('host attachment or through the panel's Download menu') and an explicit prohibition against pasting or rebuilding download_url in chat. It also handles the locked=true case by directing the agent to offer the PDF. It does not explicitly compare this tool with sibling alternatives for retrieving or viewing a score, so it falls short of a 5.

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

All ScoreStarling toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources