Skip to main content
Glama

gc_hardware_remove

Removes a registered hardware instance from the persistent registry so it is no longer remembered after server restarts. Re-add it with gc_hardware_register if needed.

Instructions

Forget a registered hardware instance.

This removes the instance from the persistent registry so it is no longer remembered across server restarts. Use gc_hardware_register to re-add it.

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": {
      "instance_id": "<instance_id>"
    },
    "name": "gc_hardware_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYes

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?

With no annotations, the description carries the full burden and does reasonably well: it discloses what is destroyed (the registry entry), the durability semantics ("no longer remembered across server restarts"), and the recovery path via gc_hardware_register. It omits whether an active connection or running instance is affected and what happens for an unknown ID.

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 action is front-loaded in one sentence, followed by a single clarifying sentence about persistence and the inverse tool. Every sentence adds information and nothing is redundant.

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 one-parameter mutation tool with no annotations and no output schema, the description covers effect, scope, durability, and reversal, which is solid. It still leaves gaps on argument sourcing and on error/edge behavior (unknown ID, connected device), which matter for a destructive registry operation.

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, but it never mentions instance_id at all. It gives no hint about the identifier's format or where to obtain it (e.g., from gc_hardware_list). The single term "registered hardware instance" is the only indirect link to the parameter.

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?

"Forget a registered hardware instance" names a specific verb and resource, and the body clarifies the exact effect: removal from the persistent registry. It names gc_hardware_register as the inverse operation, which helps orientation. It does not, however, distinguish itself from the similarly named gc_instance_remove, so an agent must still guess at that boundary.

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 implied rather than stated: an agent can infer this is for dropping a device from the saved registry, and the mention of gc_hardware_register implies the reversal path. There is no explicit when-to-use versus when-not guidance, no prerequisite conditions, and no comparison to gc_instance_remove.

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