Skip to main content
Glama

DiscreteRate

Run Fast-Slow Drain (Damiron-Nastasi 2008)

run_fast_slow_drain
Read-onlyIdempotent

Run the Fast-Slow Drain (FSD) demo — Damiron-Nastasi 2008 oscillating tank. The canonical DRS-vs-DES event-count demonstration. Returns engine output including the event counts (DES vs DRS), tank-level trace, and cycle summary. ANTI-FABRICATION: numbers come from a real DRS engine run; quote verbatim, don't recall from training data.

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_fast_slow_drain"
  }
}

Input Schema

NameRequiredDescriptionDefault
simulation_minutesNoTotal simulation horizon in minutes. Default 100. Range 10-1000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the read-only and idempotent annotations, it discloses that results come from an actual DRS engine run, identifies the principal outputs, and instructs the agent to quote numbers verbatim rather than reconstruct them from training data. It adds little about execution cost or runtime behavior, but those are secondary concerns for this simple demo.

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?

The description is compact and front-loaded with the tool's identity and purpose. The output summary and anti-fabrication instruction each provide distinct operational value without unnecessary filler.

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?

For a read-only demo with no required parameters, the definition explains what is simulated, why the demo matters, what the engine returns, and how its numerical results should be reported. Although there is no output schema, the named event counts, tank-level trace, and cycle summary provide sufficient output context for selection and invocation.

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 sole parameter, simulation_minutes, already has complete schema documentation, including its units, default, and allowed range. The description adds no further parameter-specific guidance, so the high schema coverage supports the baseline score of 3.

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 pairs a specific action and resource—running the Fast-Slow Drain oscillating-tank demo—with its Damiron-Nastasi 2008 context and its role as the canonical DRS-vs-DES event-count demonstration. This distinguishes it from the other run_* demos and from the conceptual explain_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Calling it the canonical DRS-vs-DES event-count demonstration gives clear context for when to select it. It does not explicitly direct agents to explain_des_vs_drs_event_complexity for conceptual questions or state when another demo would be preferable.

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