Skip to main content
Glama

Tank net filling time

bpj_eng_reservoir_time
Read-onlyIdempotent

Find time to add a specified volume with constant concurrent inflow and outflow.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "volume": "<volume>",
      "inflow": "<inflow>",
      "outflow": "<outflow>"
    },
    "name": "bpj_eng_reservoir_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
inflowYes
volumeYes
outflowYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds the steady-state constant-rate assumption, which is genuine extra context, but omits the practically important edge behavior when outflow is greater than or equal to inflow, and says nothing about the unit of the returned time.

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?

A single front-loaded sentence with no filler; the computed quantity comes first and the qualifying conditions follow. It is perhaps too terse, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter engineering calculator with no output schema and zero schema coverage, the description should at minimum state the unit/format of the returned time and the inflow-greater-than-outflow precondition. It covers the core concept but leaves those two practically relevant gaps.

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 0%, so the description must carry the burden, and it does map onto all three inputs (volume, inflow, outflow) while implying the net rate is the difference of the two flows. It does not name the parameters or resolve units or the sign condition, so roughly half the needed meaning is left to the schema's titles and min/max bounds.

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?

The description names a specific computed quantity (time) and the physical setup it applies to: adding a volume to a tank with concurrent inflow and outflow. It is clear enough to distinguish from unrelated siblings, but it never explicitly contrasts with them (e.g. bpj_eng_horizontal_tank), relying on the physics wording alone.

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 phrase 'constant concurrent inflow and outflow' implicitly states the applicability condition (steady rates, simultaneous feed and draw), which lets an agent infer when the tool is valid. However there is no explicit when-to-use/when-not-to-use guidance and no mention of the required precondition that inflow exceed outflow for a finite answer.

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.