Skip to main content
Glama
Sign In
headrush-mcp

headrush-mcp

by Haervwe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_routing

DestructiveIdempotent

Change a HeadRush Flex Prime signal routing without saving; use list_routings to check the slot layout first.

Instructions

Change signal routing without saving. See list_routings for the slot layout.

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": {
      "routing": "<routing>"
    },
    "name": "set_routing"
  }
}

Input Schema

NameRequiredDescriptionDefault
routingYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=true, and openWorldHint=false. The description adds meaningful behavior beyond that by clarifying the change is made "without saving," which tells the agent the mutation is non-persistent. It still does not explain how to persist the change or what exactly is affected.

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?

The description is two short sentences with no wasted wording. The core action and the non-persistent behavior are front-loaded, followed by a useful pointer to list_routings.

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?

The tool is simple, has an output schema, and benefits from annotations covering safety and idempotency. Still, the description leaves the only parameter's meaning unclear and does not explain the save/persistence path, which matters for a destructive mutation.

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

Parameters2/5

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

Schema description coverage is 0%, and the single required integer parameter "routing" is undocumented in the schema. The description only says to see list_routings for the slot layout, which gives partial context but does not explain what the integer represents, its valid range, or how it maps to slots.

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?

The description states a specific verb and resource: "Change signal routing." It also adds the important scope "without saving" and points to list_routings for layout context, though it does not explicitly distinguish this tool from siblings like set_slot_block or set_mix.

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 reference to list_routings implies a prerequisite for understanding the slot layout, which is useful usage context. However, it does not state when to use this tool versus alternatives, nor when not to use it.

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