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

blink-camera-mcp

by AbhijatSaxena
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pan_tilt_home

Move the Blink camera to its saved home position and get the final position report.

Instructions

Send the camera to its saved home position and report where it ends up.

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_home"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It accurately states the primary action and mentions reporting the ending position, but does not disclose behavior when no home position is saved, movement duration, blocking semantics, or failure modes. It is minimal but not misleading.

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 that conveys action, target state, and result with no filler. It does not repeat the tool name or schema information.

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?

The tool is simple (zero parameters) and an output schema is available, so the description's core action and result statement are largely sufficient. A small gap is the lack of a note about unset home positions, but this does not prevent correct invocation.

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 schema has zero properties and therefore 100% vacuous coverage. With no parameters to document, the baseline of 4 applies; the description adds no parameter detail because none is needed.

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 states a specific action ('Send the camera to its saved home position') with a clear resource and verb, and adds the outcome ('report where it ends up'). This distinguishes it from siblings like pan_tilt, pan_tilt_set_home, and pan_tilt_stop.

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 intended use is implied by 'saved home position' – an agent can infer this is for returning to a preset location – but the description gives no explicit when-to-use guidance, exclusions, or comparisons to related tools like pan_tilt_set_home or pan_tilt.

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