Skip to main content
Glama
Sign In

TPC Hosting Free Tools

by com.tpc-hosting
OverviewDiscussionsAdmin

Bandwidth calculator

bandwidth_calculator
Read-onlyIdempotent

Two calculations: monthly data transfer and average speed for a website (visitors, pages per visit, page size), or how long a file takes to move at a given connection speed. Decimal units unless MiB, GiB or TiB are given.

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": {
      "mode": "<mode>"
    },
    "name": "bandwidth_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYeswebsite: monthly bandwidth of a site. transfer: time to download or upload a file.
speedNotransfer: connection speed, in speed_unit.
file_sizeNotransfer: file size, in file_size_unit.
page_sizeNowebsite: average page size, in page_size_unit.
redundancyNowebsite: safety factor for spikes and bots, 1 or more. Defaults to 1.5.
speed_unitNotransfer: unit of speed. Defaults to Mbps.
file_size_unitNotransfer: unit of file_size. Defaults to GB.
page_size_unitNowebsite: unit of page_size. Defaults to MB.
pages_per_visitNowebsite: pages viewed per visit.
visitors_per_monthNowebsite: visitors per month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety is covered. The description adds a genuinely useful behavioral rule beyond them: 'Decimal units unless MiB, GiB or TiB are given,' which tells the agent how unit choice changes interpretation. It still says nothing about output shape or result units, which is the remaining behavioral gap.

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?

Two sentences, front-loaded with 'Two calculations:' and zero filler; the unit rule is appended where it is most relevant. Slightly dense — 'average speed for a website' compresses two outputs into one vague noun phrase.

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 10-parameter tool with no output schema, the description covers inputs and unit convention but never describes what comes back (result magnitude/units for each mode) or the defaults applied. Adequate to invoke, incomplete for interpreting the result.

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 100%, so every one of the 10 parameters is already described with unit and default notes, making baseline 3 appropriate. The description reinforces the decimal-vs-binary unit convention but adds no mode-conditional requirements (e.g., which params are ignored in each mode) beyond what the schema states.

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 the two calculation modes explicitly (monthly data transfer / average speed for a website, and time to move a file at a given speed), with the inputs each mode consumes. An agent can tell this apart from the other calculator siblings (subnet, chmod, uptime) without opening the schema, though the phrase 'average speed for a website' is left slightly ambiguous.

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?

Mode selection guidance exists but only implicitly, through the enumeration of the two calculations; the actual mode semantics live in the schema's mode description. There is no statement of when not to use it, no prerequisites, and no mention of alternate tools for related tasks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TPC Hosting Free Tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources