GadgetHumans API Hub

pixel_convert

Convert between pixels, points, ems and inches at a given DPI. 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": "pixel_convert"
  }
}

Input Schema

Name	Required	Description
`to`	No	Target unit
`from`	No	px, pt, em or in
`value`	Yes	Value

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed4 schema fields changedNov 3, 2026

addedInput schema / properties / from

Added value: +{
+  "description": "px, pt, em or in",
+  "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"
+]
```

AddedNov 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the operation is CPU-only and instant, implying no network dependency or side effects, but it omits precision/rounding rules, default units, and how DPI is supplied.

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 two short sentences with zero filler. The conversion purpose is front-loaded, and the performance note is compact.

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 conversion tool, it covers the units and CPU-only behavior adequately. However, the phrase 'at a given DPI' is not reconciled with the schema, which has no DPI parameter, leaving a real ambiguity about how DPI is specified.

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 repeats the supported units already present in the schema and mentions DPI, but since there is no DPI parameter in the schema, that reference adds ambiguity rather than useful parameter semantics.

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 states a specific verb and resource: converting pixels, points, ems, and inches at a given DPI. This is more specific than generic siblings like unit_convert, but it does not explicitly name or distinguish itself from those alternatives.

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 guidance on when to use this specialized pixel converter instead of unit_convert, convert_units, or page_size, nor any indication of when DPI matters. The only contextual note is that it is pure CPU and instant.

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.