Skip to main content
Glama

note_to_midi

Converts a note name such as C4 into its MIDI number (C4 = 60), giving precise pitch values for MIDI pitches, vocal melody data, or note-to-number mappings in VOCALOID6 projects.

Instructions

Note name to MIDI number (C4 = 60). / 音名を MIDI 番号に(C4 = 60)

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": {
      "note": "<note>"
    },
    "name": "note_to_midi"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. The 'C4 = 60' example usefully pins the octave convention, but it says nothing about accepted formats (sharps, flats, lowercase, negative octaves), behavior on unparseable input, or the MIDI range limits — all real concerns for a parser-style tool.

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 front-loaded and waste-free, with the key example in the first clause. The bilingual duplication doubles length without adding information, and the brevity tips into under-specification rather than tightness.

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 one-parameter converter with an output schema, no return-value explanation is needed and the octave convention is covered. Still missing is what input spellings are legal and what happens on invalid notes, which is the main thing an agent could get wrong here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter 'note' has no description, so the description must compensate — and it does partially, since 'C4 = 60' communicates the expected note-name syntax and octave numbering. Accidental spelling and case sensitivity remain undefined.

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 states a precise conversion: note name in, MIDI number out, with the concrete anchor 'C4 = 60'. It is immediately distinguishable from inverse/related siblings such as midi_to_note, though it never names an alternative explicitly.

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?

Usage is only implied by the conversion statement; there is no explicit when-to-use, when-not-to-use, or reference to the complementary midi_to_note tool. For a small utility this is probably adequate, but nothing routes the agent beyond the obvious reading of the name.

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