Skip to main content
Glama
Sign In
nina-mcp

nina-mcp

by anarcoiris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nina_disconnect_device

Disconnect any supported astronomy equipment from N.I.N.A. software to stop communication or release control.

Instructions

Disconnect a piece of equipment.

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

Input Schema

NameRequiredDescriptionDefault
deviceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The description only states 'Disconnect a piece of equipment.' It does not disclose behavioral traits such as whether disconnection is immediate, if it affects other devices, or if there are safety implications. No annotations are present to fill this gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, making it concise and easy to read. However, it is overly minimal; it could include more context without becoming verbose. The brevity leaves gaps in understanding.

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?

For a simple tool with one parameter and no output schema, the description covers the basic action. However, it lacks behavioral context and parameter semantics, which are important for an AI agent to invoke it correctly. It is minimally adequate.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the input schema provides no explanations. The description adds no information about the 'device' parameter beyond what the enum values already convey. It does not explain the impact of disconnecting each device type.

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 clearly states the action: 'Disconnect a piece of equipment.' It uses a specific verb and resource, making the purpose understandable. However, it does not distinguish itself from the sibling tool 'nina_connect_device', which is the inverse operation.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention conditions, prerequisites, or contrast with related tools like 'nina_connect_device'. An agent lacks context to choose appropriately.

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