Skip to main content
Glama

Plan shard capacity

bpj_system_shard_capacity
Read-onlyIdempotent

Size shards independently for data volume and throughput and identify the binding constraint.

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": {
      "volume": "<volume>",
      "shardSize": "<shardSize>",
      "traffic": "<traffic>",
      "shardRate": "<shardRate>"
    },
    "name": "bpj_system_shard_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumeYes
trafficYes
shardRateYes
shardSizeYes

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, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral value by saying the two dimensions are sized independently and that the computation reports which one binds, which tells the agent something about the result beyond the annotations. It does not describe the shape of that result or the units returned.

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 verb and both sizing dimensions come first and the outcome clause follows. It is efficient, though its brevity is part of why the parameter and output details are missing.

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 pure calculator with four required numeric inputs and no output schema, the definition should say roughly what comes back — shard counts per dimension and the binding constraint, presumably. It hints at the binding-constraint output but leaves the return values and the meaning of the two per-shard limits undocumented.

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 the parameter titles carry units (GiB, requests per second, GiB limit per shard, request limit per shard per second), which is most of the semantic load. The description maps 'data volume' and 'throughput' onto the inputs but never explains the pairing of shardSize with volume versus shardRate with traffic, nor how the binding constraint is derived.

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 names a specific verb ('Size') and resource ('shards') and states the two dimensions being sized against (data volume, throughput) plus the outcome (identify the binding constraint). This distinguishes it from adjacent capacity calculators like raid_capacity or units_capacity, though it never explicitly contrasts with any sibling.

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 statement of when a different capacity tool would be the right choice. The phrase 'size shards independently for data volume and throughput' implies a planning scenario but leaves the agent to infer the context entirely.

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.