Skip to main content
Glama

Resolve a MIDI note frequency

bpj_midi_note_frequency
Read-onlyIdempotent

Convert a MIDI pitch into its note name and frequency at A4 = 440 Hz.

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": {
      "value": "<value>"
    },
    "name": "bpj_midi_note_frequency"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description's one substantive addition beyond the structured data is the A4 = 440 Hz tuning assumption, which is genuinely useful because it is a fixed, non-configurable reference the caller cannot change. It says nothing about out-of-range handling, rounding/precision of the frequency, or sharp-vs-flat spelling of the note name, which are the remaining non-obvious behaviours for a pure conversion.

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?

One short sentence, front-loaded with the verb and resource, with zero filler or redundant restatement of the title. It could have used a second clause for the input format without becoming bloated, so it is efficient but perhaps over-terse.

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?

With no output schema, the description correctly takes on the job of naming the return values (note name and frequency), which it does. However, for a conversion tool the caller still lacks input format, valid MIDI range, and output precision/spelling conventions. Adequate to invoke correctly in the common case, incomplete at the edges.

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 description coverage is 0% and the single generic property named 'value' (type string, maxLength 240) carries no meaning on its own. The description partially compensates by calling it a 'MIDI pitch', which narrows the domain, but it never resolves the key ambiguity: whether the string should be a numeric note number ('60') or a scientific pitch name ('C4'), nor what range is valid. Because the schema offers nothing, more compensation was needed here than the single phrase provides.

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 specific verb and resource: convert a MIDI pitch into a note name and frequency. That is concrete enough to separate it from the numeric/frequency siblings (e.g. bpj_units_frequency, bpj_count_word_frequency), since it names both the input domain (MIDI pitch) and the two outputs. It stops short of explicitly naming a contrasting sibling, so a 4 rather than a 5.

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?

There is no explicit when-to-use or when-not-to-use statement and no reference to an alternative tool. Usage is only implied by the narrowness of 'MIDI pitch', which for a single-purpose conversion utility is a reasonable but not stated signal. An agent must infer the context of applicability entirely from the purpose statement.

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.