Skip to main content
Glama
Sign In
nina-mcp

nina-mcp

by anarcoiris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nina_sequence_load_json

Load an advanced sequence from its JSON export into NINA's sequencer. Replaces the current sequence only when no sequence is running.

Instructions

Load an entire Advanced Sequence from a raw JSON string (NINA's own sequence export format, as returned by nina_sequence_get_json). Fails if a sequence is currently running.

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": {
      "sequence_json": "<sequence_json>"
    },
    "name": "nina_sequence_load_json"
  }
}

Input Schema

NameRequiredDescriptionDefault
sequence_jsonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description provides key behavioral details (input format, failure condition) but omits side effects like whether the sequence replaces or appends, or any permissions needed. The description is adequate but not exhaustive.

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-loading the core action and format, with a key constraint. No superfluous text.

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?

For a single-parameter load tool with no output schema, the description covers the input and a key constraint. It could mention the result (e.g., loads into sequence queue) but is largely self-contained.

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 only parameter 'sequence_json' has a schema title but minimal description. The tool description compensates by specifying it expects a 'raw JSON string' in NINA's export format and referencing the getter tool, adding crucial context despite 0% schema coverage.

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 action ('Load'), the resource ('Advanced Sequence'), and the input format ('raw JSON string'). It also references the companion tool that generates the JSON, distinguishing it from sibling tools like nina_sequence_load_by_name.

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 explicitly mentions a failure condition ('Fails if a sequence is currently running'), implying when not to use it. It also ties to nina_sequence_get_json for obtaining the JSON, but does not explicitly contrast with other load methods.

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