Skip to main content
Glama

Bandwidth-delay product

bpj_system_bandwidth_delay_product
Read-onlyIdempotent

Calculate in-flight bytes needed to fill a link from decimal megabits per second and round-trip delay.

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": {
      "mbps": "<mbps>",
      "rtt": "<rtt>"
    },
    "name": "bpj_system_bandwidth_delay_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
rttYes
mbpsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this pure, read-only, idempotent, closed-world computation, so the safety profile is covered. The description adds that the result is a byte count derived from two inputs, but says nothing about edge cases (e.g., zero RTT) or how the value is rounded.

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?

A single front-loaded sentence with the verb first and the two inputs plus output unit packed in. No filler, no redundancy.

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 two-parameter arithmetic utility with no output schema, the definition covers inputs, units, and the returned quantity. Only the exact formula and rounding convention are left implicit, which is minor for a calculation this standard.

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 coverage is 0% and only bare titles are given, so the description must compensate. It does so partially by naming both inputs and flagging "decimal" megabits per second, a real disambiguation from binary, but it does not explain the allowed ranges or the maximum bound on RTT.

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 verb ("Calculate") and a concrete output ("in-flight bytes needed to fill a link"), which is a precise restatement of the bandwidth-delay product. It is distinguishable from the delay/capacity siblings, though it never explicitly contrasts itself with them.

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 narrow, self-evident purpose: supply link rate and RTT to get buffer sizing in bytes. There is no explicit when-to-use, when-not-to-use, or named alternative among the many siblings, so nothing beyond inference is offered.

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.