Skip to main content
Glama
Sign In
nina-mcp

nina-mcp

by anarcoiris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nina_camera_cool

Set the camera sensor to a target temperature in Celsius. Optionally specify a cooldown duration or cancel an active cooldown.

Instructions

Start cooling the camera to a target temperature (°C).

temperature: target sensor temperature in Celsius. minutes: cool down over this many minutes rather than immediately, if supported by the camera. cancel: if True, cancel an in-progress cooldown instead of starting one (temperature/minutes are ignored in that case).

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": {
      "temperature": "<temperature>"
    },
    "name": "nina_camera_cool"
  }
}

Input Schema

NameRequiredDescriptionDefault
cancelNo
minutesNo
temperatureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided. The description discloses the cancel behavior for in-progress cooldowns, which adds transparency. However, it does not mention potential side effects like condensation risk, return values, or safety considerations.

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 a single concise sentence followed by parameter explanations. Every sentence adds value; no wasted or redundant text. The purpose is front-loaded.

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 description adequately covers the tool's behavior and all parameters given the lack of output schema and annotations. Missing details like return format or error handling, but overall sufficient for an agent to use the tool correctly.

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?

With 0% schema description coverage, the description fully explains all three parameters: temperature (target in Celsius), minutes (gradual cooldown interval), and cancel (abort active cooldown). It adds meaning beyond the schema's default values and types.

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 the tool starts cooling the camera to a target temperature, specifying units (°C). It distinguishes from sibling tools like nina_camera_warm (warming) and nina_camera_capture (capturing).

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 description implies usage when cooling is needed but lacks explicit guidance on when to use this tool vs alternatives, prerequisites (e.g., camera connection), or exclusions (e.g., when not to use cancel).

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