Skip to main content
Glama
Sign In
ipcam-mcp

ipcam-mcp

by aidev-iprokszin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List PTZ presets

ptz_list_presets
Read-only

List saved camera positions (presets) on a pan/tilt IP camera to see which named viewpoints are available before moving to one.

Instructions

List the saved camera positions (presets) of a pan/tilt 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": "<camera>"
    },
    "name": "ptz_list_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
cameraYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only the domain fact that presets are saved pan/tilt positions, with no note on ordering, empty results, or camera-not-found behavior.

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 short, front-loaded sentence with zero filler. Nothing is wasted, though there is also very little content to structure.

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?

The output schema covers return values, so the description need not explain them, and the operation is simple. However, with a required undocumented camera parameter and no guidance on result usage, it is only minimally complete.

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% for the single required 'camera' parameter, so the description must compensate and does not. It never says whether 'camera' is an ID, a name, or an object reference, leaving the only parameter ambiguous.

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?

States a specific verb ('List') and resource ('saved camera positions (presets)') and clarifies the domain term 'presets' inline. It is distinguishable from ptz_save_preset and ptz_goto_preset by the read/list framing, though it never names those siblings.

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 is only implied: an agent can infer this is the discovery step before ptz_goto_preset, but the description never says when to use it or what to do with the results. No prerequisites or exclusions are stated.

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