Skip to main content
Glama

Two-Part Kit Availability

bpj_two_part_kit_availability
Read-onlyIdempotent

Calculate complete kits possible with two components and report remaining units of both after assembly.

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": {
      "componentA": "<componentA>",
      "reqA": "<reqA>",
      "componentB": "<componentB>",
      "reqB": "<reqB>"
    },
    "name": "bpj_two_part_kit_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
reqAYes
reqBYes
componentAYes
componentBYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 fully covered and the description adds nothing there. What it does add beyond annotations is the result shape: a count of complete kits plus the remaining units of both components, which matters because there is no output schema. It omits the arithmetic contract (integer/floor division per component, and that the binding constraint is the minimum of the two ratios), which is the main behavioral detail an agent would want.

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 sentence with no filler, front-loading the computation (kits possible) before the secondary output (remainders). Nothing is redundant and nothing needs trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small deterministic four-integer calculator with a full annotation set, the definition covers what is computed and roughly what comes back. The remaining gaps are edge-case semantics (zero stock, the limiting-component rule) and the absence of an output schema means the return description has to be inferred from one clause. Sufficient to call correctly, slightly thin on result detail.

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%, so the description should carry parameter meaning, and it only partially does: "two components" and "remaining units" imply the distinction between on-hand stock and per-kit requirement, but the four fields (componentA, reqA, componentB, reqB) are never named or explained. It relies on the schema's self-documenting titles ("Component A per kit" vs "Component A on hand") to close the gap. Adequate, but not compensating fully for the coverage gap.

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?

"Calculate complete kits possible with two components and report remaining units of both after assembly" states a specific verb (calculate), a specific resource (two-part kit counts), and the scope of the result (whole kits plus leftovers). It is clearly distinguishable from the sibling availability tools (quorum, replica, serial), which concern redundancy rather than bill-of-materials assembly. It stops short of naming any alternative, which keeps it at 4 rather than 5.

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 this applies when it has on-hand counts for two components and per-kit requirements, but the description never states when to use it, when not to, or what the adjacent options are. There is no mention of assumptions such as integer-only quantities or what happens when a component is zero.

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.