Skip to main content
Glama
Sign In
spot-ai-mcp

spot-ai-mcp

by phil-bryant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_zones

Read-only

List all zones defined on a specific camera by providing its camera_id, enabling zone lookup for Spot AI camera configurations.

Instructions

List the zones defined on a camera.

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": {
      "camera_id": "<camera_id>"
    },
    "name": "get_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault
camera_idYesCamera id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds nothing beyond the bare purpose — no pagination behavior, no ordering, no indication of what happens when the camera has no zones. With annotations present the bar is lower, but this adds essentially zero behavioral context.

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?

A single, front-loaded sentence with no filler. Nothing is wasted, though there is also very little there.

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 simple single-param read tool with annotations covering safety, this is close to adequate, but with no output schema the agent gets no hint of what a 'zone' record contains or how many are returned. A brief note on the return shape would close the gap.

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?

Only one parameter, and the schema documents it at 100% coverage ('Camera id'), so the baseline of 3 applies. The description contributes no extra meaning about the camera_id — e.g. whether it comes from list_cameras.

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?

Clear specific verb ('List') plus resource ('zones defined on a camera'), so the agent knows exactly what it returns. It does not, however, differentiate itself from siblings like get_camera or get_live_stream_urls beyond the resource name.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. The agent must infer that this is the zone-listing counterpart to get_camera purely from the resource name.

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