Skip to main content
Glama

parental_control

Destructive

Manage HomeShield parental controls per child profile on TP-Link routers: pause or resume internet, set site filters and allowed lists, and review browsing activity.

Instructions

HomeShield parental controls (local, per profile/'owner', e.g. a child). action=owners | devices | block_history (owner_id) | today_sites (owner_id) | filter_get / allowed_sites_get (owner_id) | internet_block (owner_id, blocked=true pauses the internet, false resumes) | filter_set / allowed_sites_set (owner_id, sites=[domains]) | add_owner (owner={...}) | remove_owner (owner_id).

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

Input Schema

NameRequiredDescriptionDefault
applyNofalse (default) = dry run: show the plan, diff, warnings and risk, send nothing. true = send it.
ownerNo
sitesNo
actionNoowners
revealNoShow secrets (passwords/keys) unmasked.
routerNoWhich router (see router_status 'routers'); default main.main
blockedNo
owner_idNo
confirm_tokenNoRequired with apply=true for CRITICAL changes: the token from the dry run (valid 5 minutes, bound to the exact plan and current router state).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety posture is largely covered structurally. The description does add real behavioral value by explaining semantics beyond the schema, notably 'blocked=true pauses the internet, false resumes' and that the tool is 'local, per profile/owner'. It stops short of describing the destructive-action gating (apply/confirm_token, plan-bound token valid 5 minutes), which the schema carries instead.

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?

A single pipe-delimited sentence is front-loaded with the tool's domain and then packs the action/parameter mapping densely with almost no filler. The terse pipe syntax is efficient but slightly harder to scan than a short grouped list.

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 9-parameter, destructive, nested-object tool with no output schema, the description covers actions well but omits the critical safety workflow (dry run is default, apply=true plus a plan-bound confirm_token is required for critical changes) and leaves 'owner' opaque. Those omissions are partly rescued by schema-level descriptions for apply/reveal/router/confirm_token, keeping this adequate rather than inadequate.

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 only 44% and several parameters (action, owner_id, blocked, owner, sites) have no schema descriptions, yet the description compensates by mapping each action to its required parameters and naming the sites format ('[domains]') and blocked semantics. It adds genuine meaning beyond the enum values themselves (action-to-parameter coupling). The 'owner={...}' placeholder leaves the nested object's fields unexplained, which is the remaining gap.

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 specific verb+resource domain ('HomeShield parental controls, local, per profile/owner') and then enumerates ten concrete actions (owners, block_history, internet_block, filter_set, remove_owner, etc.), so an agent immediately knows the scope. It does not explicitly contrast itself with the sibling 'access_control', so an agent must infer the boundary between the two.

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?

Usage guidance is embedded in the action list: each action is paired with the parameter it needs, which implies when to pick it (e.g. use block_history/today_sites with owner_id for reporting, filter_set/allowed_sites_set with sites for mutation). However, there is no explicit when-not guidance against the sibling 'access_control', and no mention of the dry-run-first workflow that governs the destructive actions.

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