Skip to main content
Glama
Sign In
norns-mcp

norns-mcp

by AdairBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

norns_key

Presses a monome norns key (1–3) over OSC to send down/up or press-and-release events, dry-run by default; live execution requires confirmation.

Instructions

WRITE. Press key n (1-3) over OSC; z=1 down / z=0 up, omitted = press and release. Dry run unless --live; live needs confirm=true.

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": {
      "n": "<n>"
    },
    "name": "norns_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
nYes
zNo
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With zero annotations, the description carries the full burden and does disclose the most important behavioral trait: the tool is non-destructive by default (dry run) and only performs a real write under an explicit confirm=true gate, plus the 'WRITE' marker signals mutation. It does not say what a dry run returns or how the press interacts with device state, so it stops short of a full behavioral picture.

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?

Two compact sentences, front-loaded with the mutation marker and then the mechanic, with no filler. Every clause carries either action, parameter meaning, or the safety gate.

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?

For a simple key-press tool with an output schema available elsewhere, the definition covers the action, all parameter semantics, and the dry-run/live safety model. Minor gaps remain about the OSC target/host or connection assumptions, but nothing needed to invoke it correctly is missing.

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 description coverage is 0%, yet the description defines all three parameters: n is the key index limited to 1-3, z encodes 1=down/0=up with omission meaning press-and-release, and confirm is implied as the live-mode gate. This is exactly the compensation the missing schema descriptions require.

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?

States a concrete verb and resource: press a hardware key (index 1-3) on the norns device over OSC, explicitly labeled WRITE. This clearly separates it from norns_enc (encoder turns) and norns_set_param (parameter values) in the sibling list, though it never names those alternatives itself.

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 a clear operational prerequisite: execution is a dry run unless --live is used, and live mode requires confirm=true. That is enough context to know how to actually trigger the effect, but it offers no guidance on when a key press is the right choice versus norns_enc or norns_set_param.

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