Skip to main content
Glama

client_history

Read-onlyIdempotent

Track which devices join, leave, or change IP on your TP-Link network and when. Use it to find devices that keep dropping off, filtered by MAC and time window.

Instructions

Join / leave / IP-change events recorded by this server (routers keep no such log). Shows which device keeps dropping off the network and when. Sampled every TPLINK_PRESENCE_INTERVAL seconds (default 60) while the server runs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "client_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
macNo
limitNo
since_hoursNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: data is sampled every TPLINK_PRESENCE_INTERVAL seconds (default 60) and only while the server runs, which warns the agent that the log is incomplete and has no history from before startup. It does not discuss retention or ordering, keeping it at a 4.

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?

Three short sentences, front-loaded with what the tool returns, followed by the practical use case and the sampling caveat. The parenthetical about routers earns its place; the sampling sentence is slightly dense but carries real information.

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?

An output schema exists, so return values need not be described, and the sampling caveat covers the main behavioral risk. However, with zero schema coverage on all three parameters, the definition leaves the agent without guidance on how to filter or bound the query, which is a meaningful gap for a history tool.

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% across three parameters (mac, limit, since_hours), so the description carries the full burden — yet it never mentions any of them. The only indirect link is the sampling interval, which hints at the granularity of since_hours but does not explain filtering by mac or the meaning of limit.

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?

The description names a specific resource (join/leave/IP-change event log) and a specific scope (recorded by this server, not the router), and explicitly contrasts it with router_logs by noting routers keep no such log. An agent can distinguish it from router_logs and list_clients without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete use case — identifying which device keeps dropping off the network and when — which tells the agent when this tool is the right pick. It stops short of naming an alternative or stating when not to use it, so it falls short of a 5.

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