Skip to main content
Glama
pietrodileo

IRIS MCP Blueprint

by pietrodileo

update_production_item_settings

Modify or add setting overrides for a Business Host in an InterSystems IRIS production. Persists changes; call update_production to apply them to a running instance.

Instructions

Update (or create) one or more setting overrides on an existing Business Host inside a production.

For each (name, value) entry in settings:

  • if the host already has an override with that Name and Target, its Value is overwritten;

  • otherwise a new Ens.Config.Setting is appended with the given Target.

The production is then persisted with SaveToClass + %Save. To make the changes take effect on a running production without a full restart, call update_production afterwards (equivalent to clicking "Update" in the Management Portal).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
config_nameYesConfig name of the Business Host (Service / Process / Operation) to modify.
settingsYesDict of `{SettingName: value}` pairs to apply. Values are coerced to strings before being stored.
production_nameNoProduction class name. If empty, the active production is used.
targetNoSetting target context, either `"Host"` (default) or `"Adapter"`. Applied to every entry in this batch.Host

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully bears the transparency burden. It discloses persistence method (SaveToClass + %Save), creation behavior, string coercion, and the need for a separate update step.

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?

Well-structured with clear sections. Concise yet comprehensive, front-loading the main action and using efficient phrasing.

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

Completeness5/5

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

Covers all necessary context: purpose, behavior, persistence, and post-step. Output schema exists, so return values need no description.

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

Parameters4/5

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

Schema coverage is 100% (baseline 3). The description adds value by explaining settings overwrite/append logic and the target parameter's effect, plus string coercion detail.

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 explicitly states the tool updates or creates setting overrides on a Business Host, using clear verbs and specifying the resource. It distinguishes from siblings like add_production_item and update_production.

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

Usage Guidelines5/5

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

Provides explicit guidance: describes when to use (to modify settings), explains behavior for existing vs new overrides, and instructs to call update_production afterwards for running productions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pietrodileo/iris-mcp-blueprint'

If you have feedback or need assistance with the MCP directory API, please join our Discord server