Skip to main content
Glama
Sign In
norns-mcp

norns-mcp

by AdairBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

norns_start_script

Starts a script on a monome norns, defaulting to the last remembered script. Runs as a dry run unless live mode and explicit confirmation are enabled.

Instructions

WRITE. Start a script (same as load). With no name, start the last script the norns remembers. Dry run unless --live; live needs confirm=true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "norns_start_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
scriptNo
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key behavior: writes are simulated by default, and a real start requires confirm=true. It also reveals the fallback of starting the last remembered script when no name is supplied. It omits whether starting replaces/stops the current script and what errors look like, so it is strong 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.

Conciseness4/5

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

Three short sentences, mutation marker front-loaded, no padding. The reference to "--live" is slightly confusing because no such parameter exists in the schema (only confirm), a minor wording cost.

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 two-optional-param mutation tool with an output schema (so return values need no explanation) and no annotations, the description covers the safety gate, the default behavior, and the no-name fallback. The main remaining gap is the effect on an already-running script.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does: the optional "script" argument is explained via "With no name, start the last script the norns remembers", and "confirm" is tied to the live-run requirement. It leaves open whether "script" expects an exact name, a path, or a fuzzy identifier, which is the remaining ambiguity.

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 mutating-op marker ("WRITE") followed by a concrete verb+resource: "Start a script". It also states equivalence to the sibling "load", which lets an agent place it relative to norns_load_script and norns_stop_script rather than guessing.

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?

Gives operational conditions ("Dry run unless --live; live needs confirm=true") and notes it is the same as load, so the agent learns the default is a safe no-op. It never states when to choose this over norns_load_script or what happens to the currently running script, so the when-to-use guidance is implied rather than explicit.

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