IRIS MCP Blueprint

add_production_item

Add a business host (service, process, or operation) to an InterSystems IRIS production by specifying class name, config name, and optional settings.

Instructions

Add a Business Host (Service / Process / Operation) to a production on the current namespace.

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": {
      "class_name": "<class_name>",
      "config_name": "<config_name>"
    },
    "name": "add_production_item"
  }
}

Input Schema

Name	Required	Description
`class_name`	Yes	Full class name of the host (e.g. 'EnsLib.REST.GenericService', 'MCPTest.BP.QueryService').
`config_name`	Yes	Config name of the new item inside the production.
`production_name`	No	Production class name. If empty, the active production is used.
`comment`	No	Optional comment shown in the production page.
`pool_size`	No	Pool size (jobs). Use 0 for on-demand BPL processes.
`enabled`	No	Whether the item is enabled at startup.
`settings`	No	Optional dict of {SettingName: value} pairs applied as Host settings. Typical example for a BS routing to a BP: {"TargetConfigNames": "MyBP"}

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jun 12, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states the basic action, failing to describe side effects (e.g., compilation, need for restart), error conditions, or permission requirements. This is insufficient for a tool that modifies a running production.

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

Conciseness4/5

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

The description is a single sentence that directly states the purpose, making it compact and easy to parse. It could benefit from slightly more context without becoming verbose, but it is well front-loaded.

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 tool's complexity (7 parameters, modifies a production, 26 sibling tools), the description is too sparse. It does not mention prerequisites (e.g., production must exist), the output/return value (output schema exists but not described), or how this interacts with the active production.

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?

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds no additional meaning beyond what the schema provides, so a 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 action (Add), the resource (Business Host to a production), and the context (on the current namespace). It uses specific terms like Service/Process/Operation which are meaningful in the domain, and distinguishes from sibling tools like remove_production_item or update_production_item_settings.

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 the tool is used to add a host to a production, but does not specify when to use this tool versus alternatives like create_empty_production (if production doesn't exist) or update_production_item_settings (to modify an existing item). No when-not or prerequisites are mentioned.

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