Skip to main content
Glama

DiscreteRate

Run Bottling Line SKU capacity

run_sku_capacity
Read-onlyIdempotent

Run the Bottling Line / SKU-capacity (SKU) demo — a sim-foundation parameter-set example. One 5-machine bottling line run for several products (SKUs as parameter sets). Returns, per SKU, OEE (identical ~55% — time-based interrupts) and indexed real output (swings >3x: 100 / 50 / 30 / 42) plus the pacing machine. Shows you can't read per-SKU capacity off OEE. ANTI-FABRICATION: numbers come from a real sim-foundation engine run (indexed/anonymized); 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_sku_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, closed-world); the description goes well beyond that by disclosing the return contents — per-SKU OEE at ~55%, indexed outputs of 100/50/30/42, and the pacing machine. It also adds a provenance and quoting constraint ('numbers come from a real sim-foundation engine run ... quote verbatim'), which is real behavioral guidance an agent cannot get from annotations or schema.

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 demo identity and scope are front-loaded, and every clause carries information (machines, SKUs, return values, takeaway, provenance). The heavy use of em dashes and stacked parentheticals makes it denser than necessary, but nothing is padding.

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 output schema and no parameters, the description carries the return-value burden and does so: expected OEE, output indices, and the pacing machine are all named. Remaining gaps are minor — runtime, determinism, and result shape (list vs. table) are unstated — but an agent has enough to call it and interpret results.

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?

There are zero input parameters and the input schema is empty with full coverage, so the baseline is 4. The description correctly signals the tool takes no arguments and notes that SKUs exist as internal parameter sets rather than caller-supplied inputs, which prevents an agent from hunting for a parameters object.

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 ('Run') and a specific resource (the Bottling Line / SKU-capacity demo), plus concrete scope: one 5-machine line, several SKUs as parameter sets. It is clearly distinguishable from siblings like run_chocolate_processing or run_tissue_line by the domain named. It stops short of explicitly positioning itself against those alternatives, so a 5 isn't warranted.

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 pedagogical intent ('Shows you can't read per-SKU capacity off OEE') implies when the demo is useful, but there is no explicit when-to-use statement and no sibling is named as an alternative or complement. An agent must infer selection from the demo's subject matter 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