Skip to main content
Glama

midi_to_note

Convert MIDI note numbers to note names to identify pitches when inspecting or editing VOCALOID melodies and project data.

Instructions

MIDI number to note name. / MIDI 番号を音名に

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": {
      "midi": "<midi>"
    },
    "name": "midi_to_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
midiYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden but offers no behavioral detail: it doesn't state the accepted MIDI range (0-127), what happens for out-of-range or non-integer input, or whether output uses sharps or flats. An output schema exists, so return shape is covered, but input-side behavior is not.

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?

Extremely short and front-loaded, with the input and output resources stated in order. The Japanese half is pure duplication of the English for an agent reader, which slightly dilutes density but adds no real length.

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

Completeness3/5

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

For a trivial one-parameter converter this is nearly adequate, and the output schema removes the need to explain return values. Still missing the octave-naming convention (C4 vs C3) and sharp/flat convention, which materially affect interpreting the result.

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?

The single parameter's meaning is implied by the phrase 'MIDI number', so an agent can map it to the 'midi' integer. However schema description coverage is 0%, so the description should supply the valid range and integer semantics, and it does not.

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 transformation: a MIDI number in, a note name out. This is distinct enough from the sibling note_to_midi that an agent can pick between them without opening schemas, though the description never names that inverse 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?

No when-to-use guidance, no preconditions, and no mention of the inverse tool for the opposite direction. The agent must infer usage purely from the one-line purpose statement.

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