IRIS MCP Blueprint

create_empty_production

Creates and compiles a new empty InterSystems IRIS production subclass in the current namespace via the Atelier API.

Instructions

Create and compile a new empty Ens.Production subclass in the current namespace.

Uses the Atelier REST API (PutDoc + action/compile) — same web host/credentials as other Atelier tools (IRIS_WEB_PORT, IRIS_ATELIER_API_VERSION).

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": {
      "production_class_name": "<production_class_name>"
    },
    "name": "create_empty_production"
  }
}

Input Schema

Name	Required	Description	Default
`production_class_name`	Yes	Full class name (e.g. `MyPkg.MyProduction`). Must contain at least one package segment. The `ProductionDefinition` XData will use this exact name as the production name.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jun 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions creation and compilation via Atelier API and references credentials, which adds some context. However, it does not disclose potential side effects (e.g., overwriting existing classes), error handling, or return behavior beyond what an output schema might cover.

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?

The description is two sentences long, each earning its place: first sentence states primary action, second provides essential implementation detail. There is no waste, and the most critical information (creating and compiling an empty production) is front-loaded.

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?

With an output schema present, the description does not need to explain return values. However, it lacks discussion of error conditions, compilation success criteria, or permissions. Given the tool's complexity (creation + compilation), moderate additional context would improve completeness, but current level is satisfactory.

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

Parameters3/5

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

Schema description coverage is 100%, and the parameter description in the schema is already detailed (full class name, package requirement, XData naming). The description in the tool text adds no new parameter information beyond what the schema provides, so baseline score of 3 is appropriate.

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?

The description clearly states the verb 'Create and compile' and the resource 'Ens.Production subclass'. It distinguishes itself from sibling tools like 'add_production_item' and 'update_production' by specifying it creates an empty production, leaving no ambiguity.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for creating new empty productions but does not explicitly state when to use this tool over alternatives, nor does it mention prerequisites or constraints beyond the parameter. 'Uses the Atelier REST API' provides context but not clear when/when-not guidance.

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