Skip to main content
Glama
Sign In
nina-mcp

nina-mcp

by anarcoiris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nina_connect_device

Connect a camera, mount, or other astronomy equipment by specifying a device type and optionally a target device ID. If no target is given, the currently selected device is used.

Instructions

Connect a piece of equipment. If to (a device Id from nina_list_devices) is omitted, NINA connects whichever device is currently selected in its own equipment dropdown for that category.

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": {
      "device": "<device>"
    },
    "name": "nina_connect_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
deviceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so the description carries the full burden. It discloses the behavior when 'to' is omitted but does not mention error cases, whether the tool blocks, or what happens if the device is already connected. More transparency is needed.

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?

Two sentences, front-loaded purpose, and concise explanation of optional behavior. No extraneous information.

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?

Given the tool has two parameters and no output schema, the description covers the core behavior. However, it lacks details on error handling, prerequisites (e.g., equipment must be available), and side effects, making it somewhat incomplete for a potentially state-changing operation.

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?

Schema has 0% description coverage. The description adds meaning to the 'to' parameter by specifying it is a device ID from 'nina_list_devices' and the default behavior. The 'device' parameter's enum list is self-explanatory, but no further elaboration is necessary.

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 states the tool connects equipment, which is clear. It distinguishes from the sibling tool 'disconnect_device' and explains the effect of omitting 'to'. However, it could be more specific about what 'connect' means in NINA's context.

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 explains when to omit the 'to' parameter and references 'nina_list_devices' for obtaining device IDs. It lacks guidance on when not to use this tool or alternatives like 'nina_rescan_devices', and does not 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