Skip to main content
Glama

ScoreStarling

by com.scorestarling
OverviewDiscussionsAdmin

Check recording

check_recording
Read-onlyIdempotent

Listen to an attached recording before transcribing it, free and without saving a score: its length against the account's limits, tuning, level, how many notes sound at once, and a suggested engine (null when it cannot tell what plays). Not for sheet music.

Input Schema

NameRequiredDescriptionDefault
fileYesThe attached file as the host gives it.
instrumentNoWhat the user said is playing: piano, guitar, voice, band or other.
analyze_instrumentsNotrue adds a local guess of the instruments (up to 300 seconds, about three minutes); its candidates are uncertain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / analyze_instruments / description
      Added value: +"true adds a local guess of the instruments (up to 300 seconds, about three minutes); its candidates are uncertain."
    • addedInput schema / properties / file / description
      Added value: +"The attached file as the host gives it."
    • removedInput schema / properties / instrument / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / instrument / default
      Removed value: -null
    • addedInput schema / properties / instrument / description
      Added value: +"What the user said is playing: piano, guitar, voice, band or other."
    • addedInput schema / properties / instrument / type
      Added value: +"string"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely non-derivable behavior: it is free, saves no score, reports length against account limits, and returns a null engine when the material is unrecognizable. It doesn't mention failure modes, size/format ceilings, or latency beyond what the parameter text implies.

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 front-loaded sentence beginning with the action verb, followed by the output summary and then the exclusion. Dense but every clause carries information; the embedded output list is slightly long but not padded.

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 compensates by enumerating the returned signals, and the nested file object is fully documented in the schema. What is missing is any statement of failure behavior or cost when analyze_instruments is enabled (the 300-second note lives only in the schema).

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 100%, including descriptions for file, instrument, and analyze_instruments, so the schema carries the parameter burden and baseline is 3. The description adds no syntax or selection guidance for those parameters beyond restating the suggested-engine output.

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?

Specific verb ('Listen to an attached recording') plus an explicit listing of what the check returns (length vs. account limits, tuning, level, polyphony, suggested engine). The clause 'Not for sheet music' and 'before transcribing it' cleanly separate it from transcribe_attachment and sheet-music tools.

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?

Timing guidance is explicit ('before transcribing it') and there is a clear exclusion ('Not for sheet music'), so the agent knows the precondition. It stops short of naming the sibling to call instead (e.g. transcribe_attachment or analyze_instruments) or saying what to do when the check fails.

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