Skip to main content
Glama
Sign In
UnifiyMe

UnifiyMe

by lobsterclause
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_client_details

Retrieve comprehensive details about a specific network client using its MAC address, enabling identification of device status, connection data, and troubleshooting insights.

Instructions

Get comprehensive details about a specific network client

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": "get_client_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
macYesMAC address of the client

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral transparency burden. It does convey a read-only intent through 'get', but it does not disclose what 'comprehensive details' includes, whether authentication is needed, or any edge-case behavior. This is a minimal but not misleading disclosure.

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 description is a single sentence with no filler or redundancy. It is directly front-loaded with the action and target resource, making it easy for an agent to parse quickly.

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 getter, the description is minimally viable, but the phrase 'comprehensive details' is vague and there is no output schema to clarify the return payload. It also omits any relationship to similar sibling tools, leaving the agent to infer when this tool is the right choice.

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?

The input schema fully describes the only parameter ('MAC address of the client') with 100% coverage, so the description adds little beyond the schema. This matches the baseline for high schema 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 clearly states a specific verb ('get') and resource ('specific network client'), and 'comprehensive details' signals a full-detail lookup rather than a list operation. It does not explicitly differentiate from siblings like get_client_history or get_client_dpi, but the resource and scope are reasonably distinct.

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 such as list_clients, get_device_details, get_client_history, or get_client_dpi. There are no exclusions, prerequisites, or conditions 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