GadgetHumans API Hub

percentage

Compute what X percent of Y is, what percent X is of Y, and the percent change between two numbers. 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": {
      "a": "<a>"
    },
    "name": "percentage"
  }
}

Input Schema

Name	Required	Description
`a`	Yes	First number
`b`	No	Second number
`mode`	No	of, is or change

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed4 schema fields changedNov 3, 2026

addedInput schema / properties / a

Added value: +{
+  "description": "First number",
+  "type": "number"
+}

addedInput schema / properties / b

Added value: +{
+  "description": "Second number",
+  "type": "number"
+}

addedInput schema / properties / mode

Added value: +{
+  "description": "of, is or change",
+  "type": "string"
+}

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

AddedNov 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. 'Pure CPU, instant' usefully signals no side effects and fast execution, but it does not explain error behavior, default mode, or whether b is required for each operation.

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?

The definition is two tight sentences with the operations front-loaded and no wasted filler. 'Pure CPU, instant' is slightly informal but still relevant to tool selection.

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 calculator with no output schema, the description is mostly sufficient. Still missing are the default mode, the fact that a is the only required parameter, and any differentiation from the duplicate sibling tool.

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%, so the schema already carries parameter documentation. The description clarifies the meaning of the three mode values, but it does not explicitly map X and Y to parameters a and b or state the default when mode is omitted.

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 verb and the three percentage calculations it performs, so the core purpose is clear. However, it does not distinguish itself from the sibling percentage_calculator, leaving the agent to infer which duplicate tool to use.

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 three calculation modes imply when the tool is useful, but there is no explicit guidance on when to use this tool versus the nearby percentage_calculator. No exclusions or prerequisites are stated.

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.