Skip to main content
Glama

Measured compression savings

bpj_system_compression_savings
Read-onlyIdempotent

Compare original and compressed byte counts to calculate savings, fractional change and compression ratio.

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": {
      "source": "<source>",
      "compressed": "<compressed>"
    },
    "name": "bpj_system_compression_savings"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
compressedYes

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds value by naming the three returned values (savings, fractional change, ratio), which compensates somewhat for the absent output schema, but says nothing about edge cases such as compressed exceeding source or how units/signs are reported.

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 tight sentence with the inputs front-loaded and the outputs following; there is no filler. It could be marginally better structured by separating inputs from outputs, but nothing is wasted.

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 two-integer pure calculator with rich annotations and no output schema, the description is adequate: it identifies inputs and the three outputs. It stops short of describing behavior when compressed bytes exceed source bytes (negative savings/ratio interpretation), which is the one case an agent would plausibly need to explain results.

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 0%, but the two parameters carry self-explanatory titles ('Original bytes', 'Compressed bytes') plus min/max bounds, so the practical risk is low. The description restates the same meaning ('original and compressed byte counts') without adding units, edge-case handling, or ordering rules beyond what the schema already implies.

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 concrete verb and inputs ('Compare original and compressed byte counts') and names the computed quantities ('savings, fractional change and compression ratio'), so the tool's function is unambiguous. It does not differentiate itself from the many sibling bpj_system_* calculators, but the purpose itself is clear.

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 when-to-use guidance, no mention of when not to use it, and no alternative tools named. The usage is only implicit from the purpose (call it when you have both byte counts), which leaves the agent to infer prerequisites on its own.

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.