Skip to main content
Glama
Sign In

AI SENSE Free Public Tools

by com.aisenseapi
OverviewDiscussionsAdmin

Make a MIDI file from notes

create_midi
Read-onlyIdempotent

Make a Standard MIDI File from notes written as text: tokens such as C4:4 (middle C, a quarter note), E4:8 (an eighth), R:4 (a rest) and C4+E4+G4:2 (a chord, a half note), separated by spaces or commas, with | starting a new track that plays at the same time. A note is a letter A to G with # or b and an octave -1 to 9, or a MIDI number 0 to 127. The answer carries the file as midi_base64 with its tracks, notes, tempo and length. Nothing is stored. No API key, no account and no sign up.

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": {
      "notes": "<notes>"
    },
    "name": "create_midi"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesYesThe notes, such as C4:4,E4:8,G4:8,R:4,C4+E4+G4:2.
tempoNoBeats a minute, 120 by default.
programNoThe General MIDI program, 0 (the grand piano) by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: nothing is persisted, no key or account is needed, and the response shape is spelled out (midi_base64 with tracks, notes, tempo and length). It does not cover error behavior for malformed notation.

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?

It is one front-loaded paragraph that moves purpose -> notation grammar -> return value in a sensible order with no filler sentences. The closing "No API key, no account and no sign up" is slightly promotional but still informative to an agent about auth overhead.

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 correctly takes on the job of describing the return value, and it documents the notation language thoroughly. The gaps are minor: no mention of the 4096-character input cap, the tempo/program parameters, or what happens on invalid notation.

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

Parameters5/5

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

Schema coverage is already 100%, yet the description still adds real meaning: token grammar (C4:4, E4:8, R:4, chords with +), octave range -1 to 9, MIDI numbers 0 to 127, space/comma separators, and | for a parallel track. That is substantially more than the schema's single example.

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?

"Make a Standard MIDI File from notes written as text" gives a specific verb (make), a specific artifact (Standard MIDI File), and the input form (text notation). That is enough to separate it from the sibling read_midi, which goes the opposite direction.

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?

The use case is implied clearly by the input grammar and the note that nothing is stored, but the description never states when to choose this over read_midi or any other sibling, nor any prerequisites or limits. It is adequate context without explicit routing.

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

All AI SENSE Free Public Tools toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources