InterSystems IRIS MCP Server

Overview Schema Source Related Servers Discussions Admin

interoperability_production_logs

Fetch and filter InterSystems IRIS interoperability production logs, supporting selective retrieval of errors, warnings, alerts, and info logs.

Instructions

Get Interoperability Production logs

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_logs"
  }
}

Input Schema

Name	Required	Description	Default
`item_name`	No
`limit`	No
`log_type_info`	No
`log_type_alert`	No
`log_type_error`	No
`log_type_warning`	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_logsOutput",
+  "type": "object"
+}

First observedJun 12, 2025

TDQS

D1.7/5.0

Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. 'Get' implies a read operation, but it does not explicitly state that the tool is non-destructive, nor does it mention any side effects, authentication needs, or rate limits. The behavioral information is insufficient and mostly inferred.

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 this is under-specification, not conciseness. Every word should add value; here, the description is almost redundant with the name. It fails to front-load critical information.

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?

Despite having an output schema (which could explain return values), the description still lacks essential context about what the logs contain, how to filter them, or any relationships to sibling tools. The input schema parameters are unexplained, making the tool difficult to use 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%, meaning the schema provides no parameter descriptions. The tool description does not compensate by explaining any of the 6 parameters (item_name, limit, log_type flags). Parameters like log_type_info, log_type_alert, log_type_error, log_type_warning are left entirely ambiguous.

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 'Get Interoperability Production logs' is a tautology of the tool name, repeating 'logs' without specifying the scope or distinguishing it from sibling tools like interoperability_production_create or interoperability_production_status. It lacks a specific verb-resource pair beyond what the name already implies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 its siblings. With many related tools (e.g., start, stop, status, recover), the description offers no context about appropriate usage scenarios 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