Skip to main content
Glama
Sign In
UnifiyMe

UnifiyMe

by lobsterclause
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

unblock_client

Restore network access for a previously blocked client device by specifying its MAC address.

Instructions

Unblock a previously blocked client device

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": {
      "mac": "<mac>"
    },
    "name": "unblock_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
macYesMAC address of the client to unblock

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it only restates the operation ('unblock' = undo a block). It doesn't disclose side effects, whether the device regains connectivity automatically, error behavior for an already-unblocked client, or permission requirements.

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?

Seven words, zero waste, and the core action is front-loaded. Every element ('Unblock', 'previously blocked', 'client device') earns its place, though the brevity does leave behavioral gaps that are accounted for elsewhere in the score.

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 single-parameter tool with no output schema or annotations, the description covers the core operation adequately. However, it leaves unspecified what the call returns on success, what happens for a client that isn't blocked, and how this interacts with block_client — minor gaps, but gaps nonetheless for a mutation tool.

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 description coverage is 100%, so the schema already documents the mac parameter fully ('MAC address of the client to unblock'). The description adds no parameter-level detail beyond that, which puts it at the baseline for high coverage.

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 names a specific verb ('Unblock') and resource ('client device'), and the qualifier 'previously blocked' ties it to the inverse of block_client. It's unambiguous about what the tool does, though it doesn't explicitly name siblings like block_client or reconnect_client to draw the distinction.

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?

No guidance is given on when to use this tool versus alternatives. 'Previously blocked' implies a precondition, but the description never states that this is the inverse of block_client, nor does it distinguish unblocking a device from reconnect_client or unblock_restricted_youtube.

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