Skip to main content
Glama
dnic-dev

bw-modeling-mcp

by dnic-dev

bw_create_planning_function

Creates and saves a Planning Function of a chosen type on an aggregation level, applying characteristic usage, conditions, and parameter values immediately.

Instructions

Create a Planning Function (TLOGO PLSE) of a given function type on an aggregation level. The server fills in the parameter skeleton of the function type and a usage of NONE for every characteristic; characteristic usage, conditions and parameter values can be passed right away and are applied after the create. Saved active — there is no activation step. Read an existing function of the same type with bw_get_planning_function to see which parameters a type has.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ruleNoFor function types with several rules: the 1-based rule that conditions and parameters apply to. Defaults to 1.
labelYesDescription of the Planning Function.
packageNoPackage. Defaults to "$TMP".
info_areaNoInfoArea. Defaults to the InfoArea of the aggregation level.
transportNoTransport request number. Required on systems with transport obligation.
char_usageNoCharacteristic usage per characteristic. FIELDS_TO_BE_CHANGED: the function may change its values, and records that differ in it are processed together. FIELD_FOR_CONDITIONS: not changed, but conditions may restrict it. NONE: neither. Every characteristic that is not FIELDS_TO_BE_CHANGED is a block characteristic — the function runs once per combination of their values. On a CompositeProvider the bare characteristic name is accepted as well as the prefixed one.
conditionsNoConditions of the rule, per characteristic. The given constraints replace every constraint the characteristic has; an empty or omitted constraints list removes the condition. A condition is only valid on a characteristic with usage FIELD_FOR_CONDITIONS.
parametersNoParameter values of the rule, as shown in the parameter tree of bw_get_planning_function. Applies to single-value parameters; a nested one may be named by its path ("STRUCTURE/FIELD") or, where unambiguous, by its own name. Pass value for a constant or variable for a variable reference. The FOX code of a FORMULA function is the value of its FLINE parameter. A key figure selection (e.g. KYFSEL) takes key_figures, a data selection (e.g. the from and to selections of a copy) takes selection. In a table parameter row n of every field belongs together; row = current rows + 1 adds a row.
function_typeYesPlanning function type (e.g. "0RSPL_FORMULA", "0RSPL_COPY", "0RSPL_DELETE", or a custom type).
aggregation_levelYesAggregation Level the function works on (e.g. "OBJECT_NAME").
planning_function_nameYesTechnical name of the new Planning Function, at most 20 characters (e.g. "OBJECT_NAME").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.8.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the server fills the parameter skeleton, defaults each characteristic to usage NONE, applies supplied usage/conditions/values after create, and that the object is saved active with no activation step. It doesn't cover permissions or transport-obligation behavior beyond the schema, leaving a minor gap.

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?

Three front-loaded sentences: what is created, how defaults/application behave, and where to look up parameters. Dense but every sentence carries actionable information with no filler.

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?

For an 11-parameter mutation tool with no annotations and no output schema, the description covers creation semantics, default behavior, and parameter lookup adequately. It leaves the return value (e.g. confirmation or created object identity) undiscussed, which is the only notable gap.

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 description coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not: defaults for rule (1-based), the sequencing of characteristic usage/conditions/parameter application, and pointer to the parameter tree of bw_get_planning_function as the source of valid parameter names.

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?

States a specific verb, resource and scope ('Create a Planning Function (TLOGO PLSE) of a given function type on an aggregation level'), and names the read-side sibling bw_get_planning_function so the agent can distinguish it from get/update variants without opening a schema.

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

Usage Guidelines4/5

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

Gives clear context ('saved active — there is no activation step') and routes to bw_get_planning_function to discover which parameters a type has before creating. It stops short of explicit when-not-to-use or a direct contrast with bw_update_planning_function, so it's clear context rather than full exclusion guidance.

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