Skip to main content
Glama
Sign In
InterSystems IRIS MCP Server

InterSystems IRIS MCP Server

by caretdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

interoperability_production_update

Update an Interoperability Production on InterSystems IRIS, with optional timeout and force parameters to control the update process.

Instructions

Update 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_update"
  }
}

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_updateOutput",
+  "type": "object"
+}
  2. First observed

TDQS

D1.5/5.0
Behavior1/5

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

With no annotations, the description carries full burden but only says 'Update' which implies mutation. No details on side effects (e.g., downtime, idempotency), authorization needs, or behavior of optional parameters like force.

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 extremely short but lacks essential information. Conciseness is outweighed by under-specification, making it unhelpful.

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

Completeness1/5

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

Given the tool has two undocumented optional parameters and many sibling tools, the description fails to provide enough context for correct invocation. No details about output or behavior are supplied.

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% and the description does not mention the two parameters (timeout, force). The description adds no meaning beyond the schema's property titles.

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 'Update Interoperability Production' merely restates the tool name without specifying what aspect of interoperability production is updated, making it vague and not distinguishing it from sibling tools like create or start.

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 (e.g., interoperability_production_create or -recover). The description does not indicate prerequisites, context, or exclusions.

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