Skip to main content
Glama
Sign In
norns-mcp

norns-mcp

by AdairBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

norns_screenshot

Captures the monome norns screen as a PNG on your Mac. Runs as a dry run by default; set confirm=true for live capture and writing the fixed temp file on norns.

Instructions

WRITE (small). Grab the norns screen (640x384 PNG of the 128x64 display) to the Mac. It makes matron write one fixed temp file on the norns (/tmp/norns-mcp-screen.png), so it is 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_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a real side effect: matron writes a fixed path (/tmp/norns-mcp-screen.png) and the operation is a dry run unless live. That is valuable, but the phrasing is self-contradictory (a "dry run" that still makes matron write a file) and references a nonexistent `--live` switch, so an agent cannot tell exactly what is mutated when confirm=false.

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 with the operation class ("WRITE (small)") front-loaded and zero filler. Minor cost: the terse "WRITE (small)" and unexplained `--live` token are cryptic rather than economical.

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 explained, and the description covers the key side effect, the file path, and the confirm requirement for a one-parameter tool. It falls short only on the exact dry-run semantics and why it is classified as a write despite being default-safe.

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 0% and the single `confirm` boolean has no description, so the description must compensate. It does say "live needs confirm=true," which gives the flag meaning, but it never states what confirm=false actually does beyond a vague "dry run," and the `--live` reference does not map to any schema field.

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?

"Grab the norns screen (640x384 PNG of the 128x64 display)" gives a concrete verb, resource, and output format, and no sibling tool does screen capture, so it is easily distinguished. The delivery target is muddled though: it says "to the Mac" but then describes a temp file written on the norns, leaving it unclear where the PNG actually ends up.

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?

It implies a safe default ("dry run unless --live; live needs confirm=true"), which is usable guidance for the confirm flag. However, it names a `--live` CLI flag that does not exist among the tool's parameters, and gives no guidance on when to capture a screen versus using norns_status or norns_logs to inspect device state.

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