Skip to main content
Glama
Sign In
openclaw-control-mcp

openclaw-control-mcp

by smurfy92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

openclaw_device_pair_remove

Remove a paired device from the OpenClaw gateway. The device must re-pair to reconnect.

Instructions

Remove a paired device from the gateway. Wraps device.pair.remove. Destructive — the device will need to re-pair to reconnect.

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

Input Schema

NameRequiredDescriptionDefault
deviceIdYesDevice id (hex) to unpair
instanceNoOptional OpenClaw instance to route this call to (e.g. 'default', 'work'). Falls back to the active default instance, or the OPENCLAW_GATEWAY_URL/TOKEN env vars when set. List configured instances with openclaw_setup_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.8/5.0
Behavior3/5

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

Discloses destructive nature and consequence of re-pairing, but lacks details on prerequisites, idempotency, or behavior when device isn't paired. No annotations to supplement.

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?

Two concise sentences: first defines action, second adds critical warning. No unnecessary words, information is front-loaded.

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?

Adequately covers purpose and a key consequence for a simple removal tool. Could mention that device must already be paired for action to succeed, but overall sufficient.

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 already describes both parameters with 100% coverage. Description adds no additional meaning beyond the schema's field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Remove a paired device from the gateway' with a specific verb and resource. Distinguishes from sibling tools like list, approve, reject by naming the action.

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?

Only implies usage through the destructive warning ('device will need to re-pair to reconnect'). No explicit when-to-use, alternatives, or exclusions are provided.

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