Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

page_size

Return dimensions and aspect ratio for paper sizes such as A4, A3, Letter and Legal, in mm, inches and pixels 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": {
      "size": "<size>"
    },
    "name": "page_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
dpiNoResolution for pixel size
sizeYesSize name such as A4

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed3 schema fields changed
    • addedInput schema / properties / dpi
      Added value: +{
+  "description": "Resolution for pixel size",
+  "type": "integer"
+}
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Size name such as A4",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "size"
+]
  4. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reasonably well: "Pure CPU, instant" signals a deterministic, side-effect-free, low-latency computation with no external auth or network needs. It also discloses the return shape (dimensions and aspect ratio in three units). It does not say what happens for an unrecognized size name or whether dpi has a default, which keeps it below 5.

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 tightly packed sentences, front-loaded with the primary purpose and output units, then a latency note. No redundant or filler wording; every clause carries information.

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

Completeness4/5

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

There is no output schema, so the description must explain the return value — and it does, naming dimensions, aspect ratio and the three unit systems. What remains missing is edge-case behavior (invalid size name, default DPI) and any cross-reference to `paper_sizes` to prevent misselection.

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%, with both params already documented, so the baseline is 3. The description reinforces that `dpi` drives the pixel output and that results come in mm, inches and pixels, but adds no format, default, or validation semantics beyond the schema.

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?

States a specific verb and resource ("Return dimensions and aspect ratio for paper sizes") and names concrete examples (A4, A3, Letter, Legal) plus the three output units. However, it never differentiates itself from the sibling tool `paper_sizes`, which an agent could easily confuse with this one, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the examples (look up standard paper dimensions) but there is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives. The presence of a near-duplicate sibling `paper_sizes` makes this omission more costly than usual.

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