Skip to main content
Glama
Sign In
norns-mcp

norns-mcp

by AdairBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

norns_enc

Turn a monome norns encoder (1–3) by a delta over OSC; writes are dry-run by default and live changes require confirmation.

Instructions

WRITE. Turn encoder n (1-3) by delta (-64..64, not 0) over OSC. 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>",
      "delta": "<delta>"
    },
    "name": "norns_enc"
  }
}

Input Schema

NameRequiredDescriptionDefault
nYes
deltaYes
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 burden and does disclose the essentials for a mutation tool: it is explicitly a WRITE, it defaults to a no-op dry run, and going live requires an explicit confirm=true token. It stops short of saying whether encoder changes are reversible or what a failure looks like, but the safety profile is substantially better than an unannotated mutation usually gets.

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 sentences, front-loaded with the write marker and the action, then the safety condition. Nothing is padded and the constraints are embedded inline rather than in prose.

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?

An output schema exists so return values need not be described, and the description covers action, parameter bounds, and the dry-run/confirm gate — the things an agent needs to call it safely. The unexplained '--live' toggle is the remaining hole, since it implies a mode switch the schema does not expose.

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 0%, so the description must carry all param meaning, and it does: n is bounded to 1-3, delta is bounded to -64..64 and must be non-zero, and confirm gates live execution. The one wrinkle is the unexplained '--live' flag, which is not a schema parameter and leaves the reader guessing how live mode is enabled, but the three declared params are all given operative meaning the schema lacks.

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?

Opens with a 'WRITE' marker and states a specific action: turn encoder n by delta over OSC. The resource (a hardware encoder on a norns device) is unambiguous, though it never names a sibling such as norns_key or norns_set_param to sharpen the boundary.

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 description gives a real operational precondition — dry run by default, live mode requires confirm=true — which is genuine usage guidance. However, it offers no guidance on when to reach for this tool versus norns_key, norns_set_param, or norns_load_script, so the agent must infer selection from the resource name alone.

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