Skip to main content
Glama

Estimate origin transfer

bpj_system_origin_transfer
Read-onlyIdempotent

Calculate bytes still transferred from origin using the byte-weighted cache hit fraction.

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": {
      "delivered": "<delivered>",
      "hit": "<hit>"
    },
    "name": "bpj_system_origin_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
hitYes
deliveredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered structurally. The description adds only the computational concept, not behavior: it never says what the return value looks like, and there is a units tension between 'bytes' in the description and 'GiB' in the input schema that goes unresolved. With annotations doing the heavy lifting, a 3 fits.

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 or repetition. It is arguably too short for a tool whose output units are unstated, but on structure and economy of words it is strong.

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?

A simple two-parameter pure calculator with no output schema, no nested objects, and full required-parameter coverage — a low bar for completeness. The description still leaves the output units ambiguous ('bytes' from a GiB input) and gives no sense of the arithmetic, which is the one thing a pure calculation tool needs to convey.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% in prose, but the schema carries descriptive titles with units and bounds ('Byte hit fraction', 'Edge-delivered GiB'), so the parameters are already largely self-documenting. The description contributes real meaning by specifying the hit fraction is byte-weighted, which is exactly the ambiguity an agent would otherwise face, though it does not state how the two inputs combine.

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 ('Calculate') and a precise resource ('bytes still transferred from origin'), plus names the mechanism ('byte-weighted cache hit fraction'). It is clearly distinguishable from siblings like bpj_page_transfer_budget or bpj_system_bandwidth_delay_product by domain, though it never names an alternative to route against.

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 purpose implies usage — you call it when you have an edge-delivered volume and a hit fraction and want the origin egress remainder — but there is no explicit when-to-use, no prerequisite statement, and no exclusion pointing to a sibling. Guidance is implied by the formula 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.