Skip to main content
Glama
Sign In
doricomcp

doricomcp

by kulbiq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_pitch

Change a note's pitch and spelling in place while preserving its id, rhythm, slurs, and articulations.

Instructions

Change one note's pitch and spelling (e.g. "F#4", "Ebb5") in place: it keeps its id, rhythm, slurs and articulations.

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": {
      "event_id": "<event_id>",
      "pitch": "<pitch>"
    },
    "name": "set_pitch"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowNo
pitchYes
event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does meaningfully address it: it declares the operation is in-place and enumerates what survives the edit (id, rhythm, slurs, articulations). It does not cover error behavior for invalid pitch strings or malformed event ids, so disclosure is good but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the action front-loaded and the preservation guarantee and format examples attached as supporting detail; nothing is redundant or padding.

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 simple three-parameter mutation tool with no annotations and no output schema, the description covers the essential intent and the pitch format, but leaves one of three parameters (`flow`) entirely unexplained even though the schema provides zero descriptions. Adequate minimum, with a clear gap.

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%, so the description must compensate; it does so for `pitch` by giving concrete spellings ('F#4', 'Ebb5'), which conveys the expected pitch-string format including accidentals and octave. `event_id` is only obliquely implied by 'one note ... keeps its id', and the `flow` parameter is never mentioned at all.

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 and resource ('change one note's pitch and spelling ... in place') and pins the scope to a single note, which cleanly separates it from add_notes or bulk/interval tools among the siblings. The inline examples ('F#4', 'Ebb5') make the operation concrete without opening the schema.

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 implied rather than stated: 'in place' and 'keeps its id' signal an edit-existing-note operation, so an agent can infer this is the mutation path and not a creation path. However, there is no explicit when-to-use/when-not framing and no naming of alternatives such as add_notes for creating notes.

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

Deploy Server

Other Tools