Skip to main content
Glama

Convert Guitar Tab to Piano Notes

tab_to_piano_notes
Read-onlyIdempotent

Read six-string ASCII guitar tab in standard tuning and return the sounding pitches as piano notes, in the order they appear. Returns events (column position, MIDI numbers, and the string and fret behind each note), warnings, and a link to the browser converter. Tab spacing carries no rhythm, so durations are never inferred. No Guitar Pro files or audio.

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": {
      "tab": "<tab>"
    },
    "name": "tab_to_piano_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabYesPlain-text tab with six lines from high e to low E, for example "e|--0--|" on the first line. Several tab blocks may follow each other.
capoNoCapo fret; every note sounds this many semitones higher. 0 means no capo.

Output Schema

NameRequiredDescriptionDefault
resultYes
warningsYesLimits the user should know, such as missing rhythm.
browserToolYesLink to the matching free browser tool on clefdrills.com, to share with the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / capo / description
      Added value: +"Capo fret; every note sounds this many semitones higher. 0 means no capo."
    • addedInput schema / properties / tab / description
      Added value: +"Plain-text tab with six lines from high e to low E, for example \"e|--0--|\" on the first line. Several tab blocks may follow each other."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "browserTool": {
      +      "description": "Link to the matching free browser tool on clefdrills.com, to share with the user.",
      +      "type": "string"
      +    },
      +    "result": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "events": {
      +          "description": "One entry per tab column that has notes: index, block, column, midis, and sources (string, fret, midi).",
      +          "items": {
      +            "additionalProperties": true,
      +            "properties": {},
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "warnings": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "events",
      +        "warnings"
      +      ],
      +      "type": "object"
      +    },
      +    "warnings": {
      +      "description": "Limits the user should know, such as missing rhythm.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "result",
      +    "warnings",
      +    "browserTool"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent, non-destructive read, so the description sensibly spends its words on behavior instead: durations are never inferred from tab spacing, and warnings may be returned. That rhythm caveat is genuinely useful information an agent cannot get from the annotations, though retry/error behavior is left unstated.

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?

Four tight sentences, front-loaded with the operation and transformation direction, each contributing scope or behavior. The sentence enumerating return fields is partly redundant given a declared output schema.

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

Completeness5/5

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

For a two-parameter pure-transformation tool, the description covers input format, tuning assumption, output content, and the critical limitation that rhythm is not inferred. With annotations and an output schema also present, an agent has everything needed to call this correctly.

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%, so both `tab` and `capo` are already documented in the schema. The description reinforces standard tuning and six-string formatting but adds no new meaning about capo semantics or the multi-block input convention beyond what the schema states.

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?

States a specific verb+resource pair (read ASCII guitar tab, return piano notes) with the transformation direction made explicit. The scope clauses (six-string, standard tuning, in-order) let an agent distinguish this from the sibling chord tools immediately.

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?

Gives clear applicability context and explicit exclusions: no Guitar Pro files and no audio input. It also rules out rhythmic interpretation. However, it never names an alternative tool or states what to do when input falls outside the accepted format.

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.

Resources