Skip to main content
Glama
Sign In
InterSystems IRIS MCP Server

InterSystems IRIS MCP Server

by caretdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

interoperability_production_stop

Stop an interoperability production in InterSystems IRIS. Supports optional timeout and force parameters for controlled shutdown.

Instructions

Stop 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_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNo
forceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "interoperability_production_stopOutput",
+  "type": "object"
+}
  2. First observed

TDQS

D1.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure, but it only states the action 'stop'. It does not describe whether shutdown is graceful or forceful, what state the production enters, or whether it is reversible. Side effects or required permissions are ignored.

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?

While extremely concise, the description is too sparse to be useful. It sacrifices necessary detail (parameter explanations, behavioral notes) for brevity. A well-structured description would front-load the key action and then elaborate on parameters and usage in a clear hierarchy.

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 existence of an output schema and two optional parameters, the description is incomplete. It fails to explain what the output signifies (success confirmation, status code, etc.) or how errors are handled. The complexity is low, but the description still leaves significant gaps for an agent to invoke the tool correctly.

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?

Schema description coverage is 0%, yet the tool description adds zero information about the two parameters ('timeout' and 'force'). Their purpose, allowed values, and interaction (e.g., does 'force' override 'timeout'?) are left entirely ambiguous. The schema provides only titles, not descriptions.

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

Purpose2/5

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

The description 'Stop an Interoperability Production' merely restates the tool name, providing no additional context or nuance. It does not differentiate from sibling tools like 'interoperability_production_start' or 'interoperability_production_update' beyond the verb, and fails to clarify what constitutes a 'production' in this context.

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 when not to use it. The description omits any prerequisites (e.g., production must be running) or the implications of the 'force' parameter. A helpful description would contrast this with 'interoperability_production_recover' or 'interoperability_production_status'.

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