Skip to main content
Glama
Sign In
UniFi MCP

UniFi MCP

by frousselet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

protect_get_sensor

Retrieve detailed information about a specific Protect sensor by providing its sensor ID.

Instructions

Get detailed information about a specific Protect sensor.

Args: sensor_id: The sensor ID.

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": {
      "sensor_id": "<sensor_id>"
    },
    "name": "protect_get_sensor"
  }
}

Input Schema

NameRequiredDescriptionDefault
sensor_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It indicates a read-only operation (get) with no side effects, but lacks details on permissions, rate limits, or response format.

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?

Two sentences, front-loaded with purpose, no wasted text. Efficient and clear.

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?

With a simple single-parameter operation and an output schema, the description adequately explains the tool's purpose. Could add more behavioral context, but sufficient for basic use.

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?

The description for sensor_id is minimal ('The sensor ID'), adding little beyond the schema title. Schema coverage is 0%, so description should provide more meaning.

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 clearly states the verb 'Get' and the resource 'specific Protect sensor', distinguishing it from list or update tools.

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?

The description implies use when you need detailed info on a specific sensor, but does not explicitly state when to use versus alternatives like protect_list_sensors.

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