Skip to main content
Glama
Sign In
nina-mcp

nina-mcp

by anarcoiris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nina_list_devices

Lists detected devices for a chosen category, returning IDs to use with nina_connect_device.

Instructions

List the devices NINA's device chooser sees for a given category (e.g. every ASCOM/native mount driver detected), each with an Id you can pass to nina_connect_device.

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

Input Schema

NameRequiredDescriptionDefault
deviceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so the description must cover behavioral traits. It describes the tool as listing devices (read-only), but does not mention safety, side effects, or permissions. Adequate but not explicit.

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 with purpose, no wasted words. Efficiently conveys the tool's function and how to use its output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter, the description is complete: it explains what the tool does, what the parameter means, and what the output can be used for. No output schema needed.

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

Parameters3/5

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

Schema coverage is 0%, so the description compensates partially by explaining the 'device' parameter as a category (e.g., mount driver detection). However, it does not detail each enum option individually.

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 that the tool lists devices for a given category, using specific verbs ('List') and resource ('devices'). It differentiates from sibling tools like nina_connect_device by indicating the output can be used there.

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?

The description implies usage before connecting to a device, with the example of passing the Id to nina_connect_device. It does not explicitly exclude cases or name alternatives, but the context is clear among siblings.

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