InterSystems IRIS MCP Server

by caretdev

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

interoperability_production_start

Start a specified Interoperability Production to activate message processing and services in InterSystems IRIS.

Instructions

Start an Interoperability Production

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "interoperability_production_start"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Jan 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "interoperability_production_startOutput",
+  "type": "object"
+}

First observedJun 12, 2025

TDQS

D1.9/5.0

Behavior1/5

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

The description only says 'Start', providing no information about side effects, required permissions, or state changes. With no annotations, the agent gets no behavioral clues beyond the tool name.

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

Conciseness2/5

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

The description is a single sentence but severely under-specified. It lacks necessary detail to be useful, failing to achieve appropriate conciseness that balances brevity with completeness.

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

Completeness2/5

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

Given the complexity of a production start operation and the presence of multiple sibling tools, the description is too minimal. It does not leverage the existing output schema or provide enough information for correct tool selection and invocation.

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

Parameters1/5

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

The sole parameter 'name' has no description beyond its schema title. With 0% schema description coverage, the tool description fails to explain what 'name' refers to (e.g., production name, file path), leaving agents to guess.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Start an Interoperability Production' indicates a verb and resource but is vague. It does not clarify whether it starts a new production or an existing one, especially given sibling tools like 'interoperability_production_create' and 'interoperability_production_recover'.

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 like 'create' or 'recover'. The description omits any context about prerequisites or appropriate scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server