Skip to main content
Glama

Page transfer budget

bpj_page_transfer_budget
Read-onlyIdempotent

Total measured compressed KiB and identify the largest resources and any budget overage.

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": {
      "assets": "<assets>",
      "budget": "<budget>"
    },
    "name": "bpj_page_transfer_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsYes
budgetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety bar is low. The description adds that output includes the total, the largest resources, and any overage, which is useful, but it says nothing about format, units handling, or whether it fails or just reports when over budget.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence that is front-loaded and wastes no words, but it is grammatically incomplete and too terse to convey the operation, so brevity comes at the cost of clarity.

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?

With two required parameters, no output schema, and a freeform multi-line input format, the description should explain the input line format and what the report contains. Instead it omits both, leaving an agent to reverse-engineer the expected input from a schema title alone.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden and provides nothing about either parameter. The required 'assets' string format (one 'name | KiB' per line, max 6000 chars) and the budget bounds are only hinted at by schema titles, not explained in prose.

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 description names the domain (compressed KiB totals, largest resources, budget overage) but is a noun-phrase fragment with no verb, so it never states that the tool computes/checks anything. It also gives no basis for distinguishing it from the sibling bpj_page_meta_budget, which plausibly covers a related budget check.

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 prerequisites, and no mention of alternatives such as bpj_page_meta_budget. The agent must infer from the title alone that this is a page-weight-vs-budget evaluation.

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.