Skip to main content
Glama
Sign In
nina-mcp

nina-mcp

by anarcoiris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nina_camera_warm

Warm up the camera by turning off the cooler. Optionally set a duration for gradual warming or cancel an existing warmup process.

Instructions

Warm the camera back up (turn off/ramp down the cooler).

minutes: warm up over this many minutes rather than immediately. cancel: if True, cancel an in-progress warmup instead of starting one.

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

Input Schema

NameRequiredDescriptionDefault
cancelNo
minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Discloses the two modes of operation (start warmup over minutes or cancel) and mentions ramping down the cooler. With no annotations, this is sufficient for a simple tool, but could note idempotency or state effects.

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?

Extremely concise: a one-line action followed by clear parameter bullets. No unnecessary words, front-loaded with the main purpose.

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?

Covers the core functionality and parameters adequately for a simple tool with no output schema. Minor gap: does not specify behavior if called while already warming or if both parameters are set.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given 0% schema description coverage, the description fully explains both parameters: minutes for duration, cancel for canceling. This adds essential meaning beyond the schema's type information.

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 'Warm the camera back up', specifying the verb and resource. It distinguishes from sibling tools like nina_camera_cool, which likely does the opposite.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains parameters for warmup duration and cancellation, providing clear context for use. However, does not explicitly state when to use versus alternatives or mention prerequisites.

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