GadgetHumans API Hub

data_rate

Compare two quantities as a unit rate and report the percentage difference. Pure CPU, instant. Use to pick the cheaper of two packs with different sizes.

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": {
      "a": "<a>"
    },
    "name": "data_rate"
  }
}

Input Schema

Name	Required	Description
`a`	Yes	Quantity A
`b`	No	Quantity B
`a_price`	No	Price A
`b_price`	No	Price B

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed5 schema fields changedNov 3, 2026

addedInput schema / properties / a

Added value: +{
+  "description": "Quantity A",
+  "type": "number"
+}

addedInput schema / properties / a_price

Added value: +{
+  "description": "Price A",
+  "type": "number"
+}

addedInput schema / properties / b

Added value: +{
+  "description": "Quantity B",
+  "type": "number"
+}

addedInput schema / properties / b_price

Added value: +{
+  "description": "Price B",
+  "type": "number"
+}

addedInput schema / required
```
Added value: +[
+  "a"
+]
```

AddedNov 2, 2026

TDQS

B3.1/5.0

Behavior2/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, and it discloses only that the tool is 'Pure CPU, instant'. It does not say what result is returned (no output schema exists), nor what happens when only the required 'a' is supplied while b, a_price, and b_price are omitted — a major gap given the operation is inherently binary.

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?

Three short sentences with the core operation front-loaded and no wasted clauses. 'Pure CPU, instant' is marginally filler but does usefully signal latency expectations; everything else earns its place.

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

Completeness2/5

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

With four parameters, only one required, no annotations, and no output schema, the description would need to explain return shape and optional-parameter behavior. It provides neither, so an agent cannot reliably predict what it gets back or how partial input is handled.

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% and each parameter has a terse label, so baseline is 3. The description hints at the roles (quantities vs. prices, unit rate, percentage difference) but never clarifies the relationship or formula (e.g., a_price/a versus b_price/b), leaving the four fields' interplay implicit.

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?

The description names a specific operation (compare two quantities as a unit rate) plus a secondary output (percentage difference), which is more than the opaque name 'data_rate' conveys. It stops short of differentiating itself from price/percentage siblings like 'percentage_calculator', 'discount', or 'unit_convert', so an agent must infer the boundary.

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?

One concrete scenario is supplied: picking the cheaper of two differently sized packs. There is no statement of when NOT to use it and no named alternative for pure percentage math or unit conversion, which are covered by sibling tools.

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 tools Inspect

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.