Skip to main content
Glama
Sign In
blink-camera-mcp

blink-camera-mcp

by AbhijatSaxena
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pan_tilt_stop

Stop pan/tilt motor movement instantly to halt camera positioning. Use this action when you need to cease ongoing motion or ensure the mount is idle.

Instructions

Stop the mount's motors immediately. Harmless when it is already idle.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only notes that stopping is harmless when idle, but does not mention whether the call is asynchronous, what it returns, error conditions, or any side effects beyond halting motors. This is insufficient for a safety-relevant control action.

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?

The description is two short sentences with no filler. The primary action is front-loaded, and the safety note is brief and useful. Every word earns its place.

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?

For a simple tool with no parameters and an output schema, the description covers the essential action and a relevant safety edge case. It lacks detail on return behavior or potential errors, but given the minimal complexity, the description is adequate.

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?

The tool has zero parameters, so the schema coverage is trivially 100% and there is nothing for the description to clarify. Per the baseline rule for 0-parameter tools, a score of 4 is appropriate; the description adds no param details because none exist.

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 clearly states the verb 'Stop' and the resource 'mount's motors', making the primary action unambiguous. It does not explicitly contrast with sibling tools like pan_tilt_nudge or pan_tilt_home, but the purpose is self-evident and distinct from movement commands.

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 guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The description only states what it does, not the context in which it should be chosen, leaving the agent to infer.

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