Skip to main content
Glama

Hopi

by uk.co.hopi
OverviewDiscussionsAdmin

Roman numerals converter

hopi_roman_numerals_converter
Read-onlyIdempotent

Convert between numbers and Roman numerals, both directions, for whole numbers from 1 to 3999. Give a number (e.g. 2026) to get its numeral, or a Roman numeral (e.g. MMXXVI) to get the number. The direction is detected automatically from the input. Source: https://hopi.co.uk/roman-numerals-converter/

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesA whole number from 1 to 3999, or a Roman numeral using I, V, X, L, C, D and M

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
romanYes
numberYes
summaryYes
directionYes
source_urlYesThe tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / required
      Added value: +[
+  "direction",
+  "number",
+  "roman",
+  "source_url",
+  "summary"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations that already declare the operation as read-only, idempotent, and non-destructive, the description adds key behavioral details: auto-detection of direction and support for both directions. It also cites a source link. It does not discuss invalid-input behavior, but that is a minor gap for this simple conversion tool.

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 first sentence states the core purpose and constraints, followed by two helpful examples and the auto-detection note. Every sentence earns its place, and the source attribution does not clutter the guidance.

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 single-parameter converter with a full input schema, an output schema, and safety-relevant annotations, the description is complete. It covers range, direction, examples, and auto-detection, so 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.

Parameters4/5

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

The input schema already fully describes the parameter format and valid range, which establishes a baseline of 3. The description adds value by clarifying the input-to-output relationship: numbers yield numerals and numerals yield numbers, with direction auto-detected, plus illustrative examples that make parameter usage unambiguous.

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 clearly states the tool converts between numbers and Roman numerals in both directions, which is a specific verb and resource. It also gives the valid range (1 to 3999) and concrete examples, making it easy to distinguish from the many other sibling 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 explains exactly what inputs to provide and that direction is detected automatically, giving clear context for use. It does not explicitly name alternatives or when-not-to-use cases, but no sibling tool performs this same Roman numeral conversion, so the omission is minor.

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

All Hopi 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