Skip to main content
Glama
Sign In

SmartTools

by io.github.9thShini
OverviewDiscussionsAdmin

Height converter

height_converter

Convert a height between centimetres and feet/inches. Give cm, or feet (with optional inches). One inch = 2.54 cm exactly. Runs on smart-tools.xyz.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "height_converter"
  }
}

Input Schema

NameRequiredDescriptionDefault
cmNoHeight in centimetres (give this OR feet/inches)
feetNoFeet part (give this side instead of cm)
inchesNoInches part, used with feet (default 0)
localeNoLanguage for the source_url link (default en)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses the exact conversion factor ('One inch = 2.54 cm exactly'), but it does not describe the output format, rounding behavior, or what happens when both cm and feet are supplied. For a simple pure converter this is a moderate gap rather than a severe one.

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?

The description is short and front-loaded with the core purpose. The conversion factor earns its place. The final sentence 'Runs on smart-tools.xyz' is low-value filler for an agent deciding whether to invoke the tool, but it does not significantly hurt clarity.

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 low-complexity tool with fully documented parameters, the description is mostly sufficient. However, there is no output schema and the description does not state what the tool returns or how the locale parameter affects the response, so an agent cannot fully predict 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 description coverage is 100%, so the schema already documents all four parameters well. The description adds the explicit 'cm OR feet' relationship, but that is largely already present in the schema property descriptions. No meaningful extra parameter semantics are added.

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 states a specific verb and resource: 'Convert a height between centimetres and feet/inches.' It clearly distinguishes this from siblings like length_converter or weight_converter by narrowing the scope to height and naming the exact unit systems involved.

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 instruction 'Give cm, or feet (with optional inches)' clearly tells the agent how to supply input and that the two input styles are mutually exclusive. It does not explicitly name alternatives or when-not-to-use conditions, but the usage context is clear.

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

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