Skip to main content
Glama

rename_machine

Rename a machine by providing its ID and new name to update how it is identified in your norc account.

Instructions

Rename a machine.

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": {
      "id": "<id>",
      "name": "<name>"
    },
    "name": "rename_machine"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

C2.6/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 burden of behavioral disclosure and provides almost nothing. It does not say whether the rename requires admin permissions, whether it conflicts with an existing name, whether the id is a machine hostname or numeric id, or what happens to running jobs on that machine. Only the fact that it mutates state is implied by the verb.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

A single front-loaded sentence with no wasted words, but its brevity comes from under-specification rather than efficiency. It is structurally clean but carries no useful detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with no annotations and no output schema, the description should at minimum identify what the parameters mean and what the call returns. None of that is present, leaving the agent to guess at identifier semantics and side effects.

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%, so the description must compensate for two undocumented parameters, and it does not. The meaning of 'id' (which identifier?) and 'name' (new name, format, constraints) is left entirely to inference, though the pairing is loosely implied by 'rename a machine'.

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?

"Rename a machine" states a specific verb (rename) and resource (machine), which is unambiguous on its own. It gives no differentiation from siblings such as update_job, but the action itself is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus update_job or other mutating siblings, and no prerequisites or preconditions are stated. The agent must infer that a machine must already exist and that 'name' is the new value.

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