Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

angle_convert

Convert between degrees, radians, gradians and turns. 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": "angle_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget unit
fromNodeg, rad, grad or turn
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": "deg, rad, grad or turn",
+  "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.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and "pure CPU, instant" usefully signals no network call and no rate limiting. It says nothing about invalid-unit handling, error behavior, or what happens when the optional `from` unit is omitted, which matters for a conversion tool with only one required parameter.

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?

Two short sentences, front-loaded with the operation and its unit scope. Nothing is redundant and no sentence fails to earn its place.

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 three-parameter, fully documented tool this is close to sufficient, and the absence of an output schema is only a minor gap since the return is obviously a converted number. The missing pieces are default-unit behavior and error semantics, which leave an agent guessing on edge-case calls.

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; the description adds the accepted unit vocabulary that mirrors the `from`/`to` fields. It does not clarify the asymmetry that `value` is required while `from` and `to` are optional, nor what default unit applies.

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?

"Convert between degrees, radians, gradians and turns" gives a specific verb plus the exact unit set, so an agent knows precisely what the resource is. It does not distinguish itself from close siblings such as unit_convert or angle-adjacent converters, so it stops short of a 5.

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 when-to-use guidance and no mention of alternatives like unit_convert, leaving the agent to infer that this is the specialized angle-only converter. "Pure CPU, instant" describes a performance trait rather than a selection condition.

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