Skip to main content
Glama

DiscreteRate

Run Hamburger Duo (Siprelle, DES + DRS side-by-side)

run_hamburger_duo
Read-onlyIdempotent

Run the Hamburger Duo (HAM) demo — Andy Siprelle's 5-stage finite-source line, executed as both DES and DRS implementations on the same model so the event-count and throughput numbers can be compared apples-to-apples. Returns engine output for the side-by-side run. ANTI-FABRICATION: numbers come from a real 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_hamburger_duo"
  }
}

Input Schema

NameRequiredDescriptionDefault
simulation_daysNoDays to simulate. Default 7. Range 1-30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context: the numbers come from a real engine execution and must be quoted verbatim rather than paraphrased, which is a behavioral constraint the annotations do not convey. It stops short of noting expected runtime or output shape.

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?

Front-loaded with the action and the distinguishing detail, then a short return note and a compact anti-fabrication tag. Dense but every clause carries information; the parenthetical attribution is the only mildly expendable element.

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 a single optional parameter demo runner with full annotation coverage and no output schema, the description supplies what an agent needs: what runs, what is compared, and that output must be reported verbatim. The return description ('engine output for the side-by-side run') is the one soft spot — it does not indicate what fields or structure to expect.

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?

Schema description coverage is 100% — simulation_days already carries its default (7) and range (1-30) in the schema. The description adds no syntax, units, or effect-of-value guidance beyond that, so this sits at the baseline where the schema does all the work.

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 resource ('Run the Hamburger Duo (HAM) demo') and pins down what makes it distinct: a 5-stage finite-source line executed as both DES and DRS on the same model. The contrast with the explain_* siblings (which explain paradigms rather than execute) is clear 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?

The stated goal — comparing event-count and throughput apples-to-apples across DES and DRS — implies when to reach for this tool rather than a narrative explain_* tool. However, no sibling is named, no exclusions are given, and nothing says when a different run_* demo would be the better choice; usage is inferable but not explicit.

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