Skip to main content
Glama

Rename one runner device

rename_runner_device

Rename an enrolled device's owner-visible name without changing its identity, credentials, or connection.

Instructions

Changes the owner-visible name of one enrolled device without changing its identity, credentials, or connection.

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": {
      "signalRBlockId": "<signalRBlockId>",
      "deviceId": "<deviceId>",
      "name": "<name>"
    },
    "name": "rename_runner_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
deviceIdYes
signalRBlockIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the important non-effects (identity, credentials, connection unchanged), but says nothing about required permissions, name uniqueness or validation, propagation delay, or what happens on failure — substantial gaps for a mutation tool.

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?

A single front-loaded sentence with no filler; the core action comes first and the caveat second. Appropriately sized for a simple rename operation.

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?

For a simple mutation with no output schema, the description covers intent and side-effect boundaries, but leaves parameter meanings and permission requirements undocumented where the schema offers no help. Adequate but with clear gaps.

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% for three required parameters, yet the description only implicitly maps to `name` via "owner-visible name" and never mentions `deviceId` or `signalRBlockId`. It adds a little meaning (the name is owner-visible, max 100 chars per schema) but leaves two parameters entirely unexplained.

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 specific verb and resource ("Changes the owner-visible name of one enrolled device") and scopes it to a single device, which distinguishes it from revoke/execute/pairing siblings. It stops short of naming an alternative, but the action is unambiguous.

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?

Usage is only implied: the clause about not changing identity, credentials, or connection hints that this is the safe cosmetic option versus revoke/re-pair. There is no explicit when-to-use, prerequisite, or exclusion statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.