Skip to main content
Glama

Miles to kilometers

by io.github.sadri-dridi
OverviewDiscussionsAdmin

mi-to-km

Miles to kilometers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoGit ref name; discarded after the shape check
urlNoHTTPS URL to normalize or cite
cityNoCity name for a public weather hint; discarded after the call
feedNoPublic RSS or Atom URL; titles discarded
hostNoPublic hostname
jsonNoJSON text to validate; discarded after the check
pathNoFile path to check; no disk access
zoneNoIANA timezone name
queryNoSearch text; discarded after the length check
websiteNoPublic https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / website
      Added value: +{
+  "description": "Public https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.",
+  "type": "string"
+}
  2. Changed5 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
+  "description": "City name for a public weather hint; discarded after the call",
+  "type": "string"
+}
    • addedInput schema / properties / feed
      Added value: +{
+  "description": "Public RSS or Atom URL; titles discarded",
+  "type": "string"
+}
    • addedInput schema / properties / path
      Added value: +{
+  "description": "File path to check; no disk access",
+  "type": "string"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Search text; discarded after the length check",
+  "type": "string"
+}
    • addedInput schema / properties / ref
      Added value: +{
+  "description": "Git ref name; discarded after the shape check",
+  "type": "string"
+}
  3. First observed

TDQS

D1.6/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It does not state whether the call is read-only, whether inputs are discarded, whether network or file access occurs, or what output is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words are short but not usefully structured; this is under-specification rather than conciseness. There is no operative sentence explaining what a caller should provide or expect.

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

Completeness1/5

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

With 10 optional parameters, no annotations, and no output schema, an agent needs substantial context about which parameters to pass, what the conversion input actually is, and what result format to expect. The description provides none of this.

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 baseline is 3 even though the tool description adds no parameter meaning. However, the description never connects 'miles' or 'kilometers' to any schema property, and none of the declared parameters represents a distance, which prevents a higher score.

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

Purpose1/5

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

The description 'Miles to kilometers' simply restates the tool name mi-to-km and lacks a verb, resource, or operational statement. It also gives no clue how the 10 unrelated schema parameters relate to the stated conversion, so an agent cannot determine what the tool actually does.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool, when to avoid it, or which sibling tool might be more appropriate. The name implies a simple unit conversion, but the schema provides no miles input, so even the implied usage is unsupported.

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

All Miles to kilometers 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