Skip to main content
Glama

DiscreteRate

Run Vegetable Plant (Plant Builder distribution control)

run_vegetable_plant
Read-onlyIdempotent

Run the Vegetable Plant (VEG) demo — a Plant Builder distribution-control model. Two Making lines feed five Packing lines through eight surge bins; a DRS rate solver splits and rebalances the flow across the bins as the plant works through its campaign schedule. Returns the plant rollup (utilization, campaigns, active window), per-product goal attainment, per-system campaign timelines, and final surge-bin / delivered levels. 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_vegetable_plant"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the return contract and the ANTI-FABRICATION instruction telling the agent to quote numbers verbatim because they come from a real engine run. It does not mention cost, runtime, or determinism of the campaign schedule beyond the idempotent hint, which is 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?

Two tight sentences: the first establishes what is run and its internal structure, the second enumerates the returned rollups, and a trailing directive caps it off. Nothing is repeated from annotations or title, and the key identification is front-loaded.

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?

With no output schema, the description carries the return-value burden and does so explicitly: plant rollup (utilization, campaigns, active window), per-product goal attainment, per-system campaign timelines, final surge-bin/delivered levels. For a zero-parameter, closed-world demo, an agent has everything needed to call and report it.

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?

The tool takes zero parameters, so there is no parameter meaning to convey; the schema is empty and fully specified by definition. Baseline credit applies, and the description's discussion of internal components (lines, bins, DRS solver) describes the model rather than inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Run the Vegetable Plant (VEG) demo') and characterizes the model concretely: two Making lines, five Packing lines, eight surge bins, a DRS rate solver. It is clearly a distinct demo from siblings, but it never names which sibling run_* tool to pick instead, so differentiation is by subject matter only.

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 calling it a 'demo' and by the campaign/distribution framing, but there is no explicit when-to-use, when-not-to-use, or pointer to describe_demo / list_drs_demos / the other run_* demos for comparison. An agent knows what it does, not when to prefer it.

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