Skip to main content
Glama
Sign In
API Hub MCP — 337+ Tools

API Hub MCP — 337+ Tools

by scotia1973-bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

energy_convert

Convert energy values between joules, calories, watt-hours, kilowatt-hours, BTU, foot-pounds, and electronvolts.

Instructions

Convert between energy units: J, cal, Wh, kWh, BTU, ft-lb, eV.

Parameters:
    value — Energy value.
    from_unit — Source unit.
    to_unit — Target unit.

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>",
      "from_unit": "<from_unit>",
      "to_unit": "<to_unit>"
    },
    "name": "energy_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
from_unitYes
to_unitYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, and the description only states 'Convert between energy units' without disclosing any behavioral traits such as error handling, precision, or supported unit validation. This is minimal and leaves the agent guessing about edge cases.

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 extremely concise with two effective sentences: one for the purpose and one for the parameters. Every sentence adds value, and the structure is front-loaded.

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 simple unit converter, the description covers the essential functionality and parameter meanings. However, it lacks details about valid unit inputs, error behavior, or output format (despite an output schema, its content is unknown). It is adequate but not fully comprehensive.

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?

With 0% schema description coverage, the description adds meaning by listing parameters and their purposes ('value — Energy value', etc.). However, it does not specify valid unit strings or constraints, so the added value is moderate.

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 explicitly states 'Convert between energy units' and lists a specific set of units (J, cal, Wh, kWh, BTU, ft-lb, eV), making its purpose clear and distinguishing it from sibling conversion tools.

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 description implies usage for energy unit conversion but provides no explicit guidance on when not to use or alternatives. It is straightforward for such a simple converter, but lacks exclusions or comparisons to sibling tools.

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

Deploy Server

Other Tools