Skip to main content
Glama

DiscreteRate

Run Valdez Tanker (Koelling-Remy 1983)

run_valdez_tanker
Read-onlyIdempotent

Run the Valdez Tanker (VALD) demo — Koelling-Remy 1983 Alaska Pipeline model, the paradigm-integration motivator. Crude flows continuously into the Valdez Marine Terminal storage tank (Flow); tankers arrive discretely to drain it (Item); DRS handles both via F2I / I2F transitions. Returns engine output including tanker arrival/departure events and tank-level trace. 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_valdez_tanker"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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, so the safety profile is covered. The description goes beyond them by disclosing the return content — 'tanker arrival/departure events and tank-level trace' — and by adding an anti-fabrication directive that tells the agent to quote engine output verbatim rather than invent numbers. It stops short of stating runtime or output size.

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?

Three dense sentences, front-loaded with the identity of the model before the mechanics and the output/anti-fabrication note. The domain jargon (Item, Flow, F2I/I2F) earns its place by telling the agent what the simulation exercises, though the middle sentence is heavier than a tool-selection decision strictly requires.

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?

A single optional parameter, no output schema, and full schema coverage mean little is required; the description compensates by naming what comes back in the engine output. An agent has enough to call this correctly and to know not to paraphrase the numbers. Only the absence of any explicit alternative-routing keeps it from being complete.

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%, so simulation_days, its default of 30, and its 1-90 range are already fully documented in the schema. The description adds no extra semantics about how the horizon affects modeled dynamics (e.g., number of tanker arrivals), so the baseline 3 applies.

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 Valdez Tanker (VALD) demo — Koelling-Remy 1983 Alaska Pipeline model' — and describes the modeled system (continuous crude flow, discrete tanker arrivals, F2I/I2F transitions). The resource is distinct enough from siblings like run_chocolate_processing that confusion is unlikely, though it never explicitly contrasts itself with the other run_* demos or with explain_paradigm_integration.

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?

Calling it 'the paradigm-integration motivator' implies the thematic situation in which to pick it, but there is no explicit when-to-use statement, no routing to explain_paradigm_integration for conceptual explanation, and no guidance on when to choose run_showcase or another demo instead. Usage is inferable from the sibling names rather than stated.

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