Skip to main content
Glama

Raw bitmap working memory

bpj_design_bitmap_working_memory
Read-onlyIdempotent

Estimate packed, uncompressed bitmap storage from pixel dimensions, channel count, and bits per channel.

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": {
      "pixelsWide": "<pixelsWide>",
      "pixelsHigh": "<pixelsHigh>",
      "channels": "<channels>",
      "bits": "<bits>"
    },
    "name": "bpj_design_bitmap_working_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitsYes
channelsYes
pixelsHighYes
pixelsWideYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 fully covered. The description adds genuinely useful scope information with 'packed, uncompressed' — indicating no compression, padding, or container overhead in the estimate. It stops short of stating the output unit or whether alignment/headers are excluded, which matters for a storage calculator.

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?

A single front-loaded sentence that names the operation, the qualifier that scopes it, and the inputs required. There is no filler, hedging, or repetition.

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?

There is no output schema, so the description carries the burden of explaining the return value, yet it never says whether the estimate is in bytes, bits, or a human-readable string. For a four-parameter pure-calculation tool this is the main missing piece; otherwise the definition is sufficient to invoke correctly.

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%, but each property carries a title ('Bits per channel', 'Channels', 'Height (px)', 'Width (px)') and hard min/max bounds, so the parameter meanings are largely visible in the schema itself. The description names the same concepts without adding semantics the schema lacks — e.g., no typical bit-depth values or whether channels counts alpha.

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 ('Estimate') and resource ('packed, uncompressed bitmap storage'), and enumerates the three input classes it derives the estimate from. The 'packed, uncompressed' qualifier meaningfully separates it from raster/compression-oriented siblings such as bpj_design_scan_raster, though no sibling is named explicitly.

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 only implied: an agent can infer it should call this when it needs a raw storage figure for given dimensions. There is no statement of when not to use it, no mention of alternatives (e.g., compressed or export-oriented tools), and no prerequisites or constraints on valid input ranges beyond the schema.

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.