Skip to main content
Glama
Sign In
nina-mcp

nina-mcp

by anarcoiris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nina_rotator_move

Slews the rotator to a specific sky angle, accepting a target angle in degrees (0.0 to 360.0).

Instructions

Slew the rotator to a specific sky angle.

angle: Target sky position angle in degrees (0.0 to 360.0).

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": {
      "angle": "<angle>"
    },
    "name": "nina_rotator_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description does not disclose any behavioral traits such as whether the operation is synchronous, blocking, or requires the rotator to be connected.

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 extremely concise with no wasted words, using two clear sentences to convey purpose and parameter details.

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 one-parameter tool, the description covers the basics but lacks operational context like prerequisites or whether the call is synchronous.

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?

The description adds meaning to the 'angle' parameter by specifying units (degrees) and range (0.0 to 360.0), which is not present in the input schema.

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 states the specific verb 'slew' and resource 'rotator', clearly indicating the action of moving to a sky angle. It distinguishes from sibling tools like nina_rotator_stop and nina_rotator_info.

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, nor are there any prerequisites or exclusions mentioned.

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