Skip to main content
Glama

DiscreteRate

Run Chocolate Processing (Plant Builder DES↔DRS bridge)

run_chocolate_processing
Read-onlyIdempotent

Run the Chocolate Processing (CHOC) demo — Plant Builder's joint DES↔DRS bridge. Three systems in series (Bean Processing → Cocoa Powder → Chocolate): DES schedules campaigns and injects equipment failures, a DRS rate solver carries the continuous flow, a bridge couples them. Exercises all 7 controllers + Goal blocks. Returns the plant rollup (schedule occupancy vs busy utilization, total downtime, campaigns), per-product attainment, and per-system campaign timelines with downtime. ANTI-FABRICATION: numbers come from a real Plant Builder engine run; quote verbatim.

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": "run_chocolate_processing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description goes beyond that by disclosing what the run produces (plant rollup, per-product attainment, per-system campaign timelines with downtime) and by adding an ANTI-FABRICATION directive that numbers come from a real engine run and must be quoted verbatim. It still leaves out runtime/cost expectations for what is presumably a nontrivial simulation.

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 content is front-loaded: the identity and bridge framing come first, then internals, then return values, then the integrity directive. It is dense but every clause carries information; the parenthetical system chain and controller count are the only mildly expendable details.

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 no input parameters and no output schema, the description carries the burden of explaining returns, and it does so at three levels of granularity (rollup, per-product, per-system). Combined with the annotations covering mutability, an agent has enough to call it correctly; only execution-time expectations are absent.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description correctly does not waste space restating an empty schema.

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 names a specific verb ("Run") and a specific resource (the Chocolate Processing / CHOC demo) and immediately characterizes it as "Plant Builder's joint DES↔DRS bridge." It further scopes the tool by describing the three-system series and the seven controllers exercised, which lets an agent distinguish it from sibling demos such as run_showcase or run_tissue_line without opening any schema.

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?

Usage is implied by the domain framing: an agent can infer this is the tool for the CHOC three-system bridge demo. However, the description never explicitly states when to choose it over list_drs_demos, describe_demo, or the other run_* demos, and offers no exclusions or prerequisites, so routing must be inferred from the domain name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources