Hopi

Download time calculator

hopi_download_time_calculator

Read-onlyIdempotent

Estimate how long a download takes. Give a file size with its unit (MB, GB, TB) and a connection speed with its unit (Mbps or Gbps in bits per second, or MBps in bytes per second). Returns a human-readable duration and the time in seconds. Source: https://hopi.co.uk/download-time-calculator/

Input Schema

TableJSON Schema

Name	Required	Description
`size`	Yes	File size value
`speed`	Yes	Connection speed value
`sizeUnit`	Yes	File size unit
`speedUnit`	Yes	Speed unit: Mbps/Gbps are bits per second, MBps is megabytes per second

Output Schema

TableJSON Schema

Name	Required	Description
`size`	No
`speed`	No
`seconds`	No
`summary`	Yes
`duration`	No
`sizeUnit`	No
`speedUnit`	No
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)
`megabytesPerSecond`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026
- addedOutput schema / required
```
Added value: +[
+  "source_url",
+  "summary"
+]
```
First observedSep 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds useful behavioral detail by specifying the expected return values: a human-readable duration and time in seconds. It also clarifies the bit/byte distinction for speed units, which is critical to understanding how the estimate is computed.

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?

The description is compact and front-loaded: the core purpose appears in the first sentence, input requirements in the second, and output plus source in the third. Every sentence earns its place, and there is no filler or redundant restating of the tool name.

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

Completeness5/5

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

Given the simple calculator nature, rich annotations, 100% schema coverage, and presence of an output schema, the description covers everything an agent needs: purpose, required inputs, unit rules, output shape, and an attribution source. No critical gap remains for correct invocation.

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 100%, so the baseline is 3. The description adds value beyond the schema by explicitly instructing the user to provide a file size with a unit and a connection speed with a unit, and by restating the bit/byte distinction in the main text rather than leaving it only in the parameter description. This helps an agent understand the semantic intent of the parameters even before inspecting the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Estimate how long a download takes.' It clearly names the required inputs and what is returned, making the tool's purpose unambiguous. It is also distinct from sibling calculators because no other sibling offers download-time estimation, and the unit clarifications prevent confusion with converter tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use the tool: whenever a download duration needs to be estimated from file size and connection speed. It does not explicitly name alternatives or exclusions, but there is no obvious sibling tool that would compete for this exact task, so the context is sufficient.

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

All Hopi tools Inspect

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

Need Help?