Skip to main content
Glama
Sign In
nina-mcp

nina-mcp

by anarcoiris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

nina_sequence_edit

Edit specific fields within a loaded sequence using path addressing, enabling quick tweaks like exposure count or duration without reloading the entire sequence.

Instructions

Edit a single field of the loaded sequence in place, addressed by path (as shown in nina_sequence_get_json's structure). Useful for small tweaks (e.g. an exposure count or duration) without reloading the whole sequence.

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": {
      "path": "<path>",
      "value": "<value>"
    },
    "name": "nina_sequence_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Discloses in-place editing behavior, but no annotations exist to cover safety. Missing details on whether changes are immediately saved, destructive nature, or prerequisites like sequence must be loaded first.

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, no filler, front-loaded with key information. Efficient and easy to parse.

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?

Covers purpose, use case, and links to related tool for structure. Lacks prerequisites (e.g., sequence must be loaded) and return value information, but overall sufficient for a simple edit tool.

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?

With 0% schema description coverage, the description partially compensates by explaining the 'path' parameter references the structure from nina_sequence_get_json, but the 'value' parameter has no description or format guidance, leaving ambiguity for the agent.

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?

Description clearly states the tool edits a single field of the loaded sequence by path, referencing the structure from nina_sequence_get_json, and provides a use case for small tweaks. This uniquely identifies its purpose among many sibling sequence tools.

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?

Explicitly mentions it is useful for small tweaks without reloading the whole sequence, implying when to use. However, it does not state when not to use or mention alternatives like reloading or using other edit tools.

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