Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

energy_convert

Convert energy units: joules, calories, kWh and BTU. Pure CPU, instant.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "value": "<value>"
    },
    "name": "energy_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget unit
fromNoSource unit
valueYesValue

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed4 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Source unit",
+  "type": "string"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "Target unit",
+  "type": "string"
+}
    • addedInput schema / properties / value
      Added value: +{
+  "description": "Value",
+  "type": "number"
+}
    • addedInput schema / required
      Added value: +[
+  "value"
+]
  4. Added

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden; it does disclose that the operation is pure CPU and instantaneous, implying no side effects or network calls. However, it says nothing about accepted unit string formats, case sensitivity, what happens with an unsupported unit, or how missing from/to are resolved.

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?

Two short sentences, front-loaded with the resource and units, with no filler. It could have spent the second sentence on the accepted unit format rather than the 'pure CPU, instant' reassurance, which is nearly redundant for a converter.

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?

There is no output schema, so the description would need to convey what comes back (a bare number, an object with units?) and it does not. Combined with the optional from/to parameters, an agent can construct a call but cannot fully predict the result's shape.

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 coverage is 100% but the schema field descriptions are nearly empty ('Target unit', 'Source unit', 'Value'), and there are no enums. The description adds real value by naming the unit families, yet it never states the accepted tokens for 'from'/'to' or what the default source unit is when only 'value' is supplied.

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

Purpose4/5

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

States a specific verb and resource ('Convert energy units') and enumerates the supported units, so the domain is unmistakable. It does not distinguish itself from the many convert siblings, notably the generic 'unit_convert' and the other dimension-specific converters, so an agent still has to infer which one to pick.

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?

Usage is only implied by the domain ('energy units'), with no explicit when-to-use/when-not or reference to alternatives like unit_convert. 'Pure CPU, instant' gives a hint that this is a local computation with no external dependency, but it is not framed as selection guidance.

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

All GadgetHumans API Hub 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