Hopi

Kg to stone converter

hopi_kg_to_stone

Read-onlyIdempotent

Convert a weight in kilograms to UK stone and pounds. Returns whole stone plus remaining pounds, and the totals in pounds and decimal stone. Source: https://hopi.co.uk/kg-to-stone/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kilograms`	Yes	Weight in kilograms

Output Schema

TableJSON Schema

Name	Required	Description
`stone`	No
`pounds`	No
`summary`	Yes
`kilograms`	No
`source_url`	Yes	The tool's page on hopi.co.uk (cite or open to check the figure)
`totalStone`	No
`totalPounds`	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.1/5.0

Behavior4/5

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

Annotations already mark it read-only, idempotent, and non-destructive; the description adds behavior beyond that by specifying that output includes whole stone, remaining pounds, total pounds, and decimal stone. It also cites the source. It does not detail rounding or precision, but for a simple converter this is adequate.

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?

Two concise sentences front-load the conversion action and then specify return structure, followed by a source citation. No filler or redundancy.

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?

For a one-parameter, read-only converter with an output schema present, the description covers the conversion direction, output format, and source. An agent has everything needed to select and invoke the tool correctly.

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?

The schema already fully describes the single parameter ('Weight in kilograms') at 100% coverage. The description restates the input's role but adds no new semantic detail such as precision or accepted range beyond the schema's minimum constraint.

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?

Description plainly states the conversion action and target units: 'Convert a weight in kilograms to UK stone and pounds.' It also clarifies output composition and the UK-specific unit variant, distinguishing it from the more generic hopi_weight_converter.

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 tool's purpose is clear, so when to use it is implied, but the description never mentions alternatives or exclusion conditions. It does not say to prefer hopi_weight_converter or another converter for other unit conversions, leaving routing to inference.

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?