Skip to main content
Glama

DiscreteRate

Run Tissue Line strategic decision

run_tissue_line
Read-onlyIdempotent

Run the Tissue Line (TIS) demo — a sim-foundation parameter-set example. One tissue line (Reel supply → Converter → Winder), three strategic decisions (each a parameter set): bypass converter / run converter / add storage tower. Returns per-decision throughput as % of nameplate (75.4 / 75.4 / 73.4), the binding bottleneck (the upstream parent-reel supply in all three), and converter/storage detail. Shows the downstream decision barely moves throughput — invest at the constraint. 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_tissue_line"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), so the description's added value is describing the return payload — per-decision throughput percentages, the binding bottleneck, and converter/storage detail. It also discloses provenance and an anti-fabrication quoting requirement, which is genuine behavioral guidance absent from the structured fields.

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 purpose is front-loaded in the first clause, followed by scenario structure, then expected outputs and the interpretive takeaway. It is dense but each element (line topology, decision set, output shape, constraint insight, provenance) carries information; only the literal 75.4/75.4/73.4 figures risk being noise before a run.

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 still enumerates what comes back (throughput per decision, binding bottleneck, converter/storage detail), what the scenario contains, and how to report results. Nothing an agent needs in order to call and interpret this no-arg tool is missing.

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; baseline for a no-arg tool is 4. The description correctly presents the three strategic decisions as fixed internal parameter sets rather than agent-supplied inputs, which prevents a misuse attempt to pass arguments.

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 and named resource ('Run the Tissue Line (TIS) demo') and immediately scopes it as a sim-foundation parameter-set example with three named decisions. This differentiates it cleanly from the many sibling run_* demo tools.

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 framing ('shows the downstream decision barely moves throughput — invest at the constraint'), so an agent can infer this is relevant for constraint/bottleneck questions. However, there is no explicit when-to-use, when-not-to-use, or comparison against siblings such as run_sku_capacity or run_chocolate_processing.

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