Skip to main content
Glama

Measure JSON field sizes

bpj_json_size_breakdown
Read-onlyIdempotent

Measure UTF-8 bytes of each compactly serialized top-level value.

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": {
      "object": "<object>"
    },
    "name": "bpj_json_size_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral detail — that values are compactly serialized (whitespace stripped) before measuring — but says nothing about what the response looks like or how nested values are handled.

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?

One tightly written sentence with no filler, and the key qualifier ('compactly serialized') is placed where it matters. It is efficient, though the brevity leaves gaps that a slightly longer definition could close.

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 read-only tool this is close to adequate, but with no output schema the description should indicate that the result is a per-key byte count (and whether nested structures are aggregated). That return-shape information is absent.

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 0% for the single 'object' parameter, so the description must carry the meaning, and it does imply the input is a JSON object whose top-level values get measured. It omits the important constraint that the input must be a valid JSON string and is capped at 6000 characters.

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 gives a specific verb ('Measure') and a precise resource ('UTF-8 bytes of each compactly serialized top-level value'), which tells an agent exactly what is computed. It does not, however, contrast itself with near neighbors such as bpj_json_string_inventory or bpj_json_node_census, so the sibling differentiation is left implicit.

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 statement of when to use this tool, when not to, or which sibling to prefer for related size/measurement questions. The agent must infer the use case entirely from the one-line purpose.

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.