Skip to main content
Glama

x402-publish-1792555488004-textkit--human-bytes

textkit — human bytes: Format a byte count as human-readable size with KB and MiB values.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-publish-1792555488004-textkit--human-bytes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

No annotations, so the description carries the full behavioral burden, and it does not meet it. It hints at output units (KB, MiB) but does not explain what a zero-parameter invocation actually operates on, whether it is a demo/sample tool (the name contains 'publish'), or what the response looks like. The absence of any note about the empty input schema is a meaningful disclosure gap.

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?

A single front-loaded sentence with no filler; the main capability is stated first. The 'textkit — human bytes:' prefix is mildly redundant with the tool name but not wasteful enough to drop below 4.

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?

For a zero-param, no-output-schema tool, the description should make clear what the call does and what comes back. Instead it leaves the central question unanswered: with no inputs, which byte count is formatted, and is this a static/demo result? No return shape is described despite there being no output schema to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate. No penalty applies, though the description also gives no explanation of why no input is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb and resource are stated ("Format a byte count as human-readable size") and the outputs (KB, MiB) are named, which is more than a restatement of the name. However, it never distinguishes itself from nearby siblings such as x402-format-bytes, x402-data-size-humanize, or x402-file-size-humanize, and the stated purpose conflicts with an empty input schema – there is no byte count parameter to format, leaving the actual operation ambiguous.

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?

No guidance on when to use this versus the many formatting/humanizing siblings (x402-format-bytes, x402-data-size-humanize, x402-number-humanize). No prerequisites, no exclusions, no context for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources