Skip to main content
Glama

find_client

Read-onlyIdempotent

Locate connected devices by matching a hostname, IP address, or MAC address against a search query, with case-insensitive matching and support for '-' or ':' MAC formats.

Instructions

Devices whose hostname, IP or MAC contains the query (case-insensitive; '-' and ':' both work in MACs).

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": {
      "query": "<query>"
    },
    "name": "find_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and repeatability are covered structurally. The description adds genuine behavioral detail the annotations do not: case-insensitive matching and that both '-' and ':' are accepted in MACs. It says nothing about result caps or behavior on zero matches, but with an output schema present that gap is minor.

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

Conciseness4/5

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

One compact sentence with zero filler, and the matching scope is front-loaded before the separator caveat. The sentence-fragment form is efficient but slightly less scannable than a verb-led statement of what the tool does.

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?

A single-parameter lookup with annotations and an output schema needs relatively little prose, and the description covers the matching rules that structured fields omit. Only the absence of any guidance versus list_clients or on empty/oversized result sets keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the single parameter, and it does: it names the three fields searched (hostname, IP, MAC), specifies substring rather than exact matching, and documents case-insensitivity and MAC separator tolerance. That is meaningfully more than the bare 'Query' property in the schema.

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 states a precise matching contract — devices whose hostname, IP or MAC contains the query — so an agent knows exactly what set comes back. It is a noun phrase rather than a verb+resource statement and never names the sibling list_clients to explain how this differs from an unfiltered enumeration, so it falls short of a 5.

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 explicit when-to-use guidance and no mention of alternatives such as list_clients for full enumeration. Usage is only inferable from the substring-matching semantics; nothing tells the agent when this tool is the wrong choice.

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