Skip to main content
Glama

Dual-Source Interruption Gap

bpj_dual_source_interruption_gap
Read-onlyIdempotent

Model disruption to the primary share of an order and deduct additional units available from a backup source.

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": {
      "demand": "<demand>",
      "fraction": "<fraction>",
      "delayed": "<delayed>",
      "emergency": "<emergency>"
    },
    "name": "bpj_dual_source_interruption_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
demandYes
delayedYes
fractionYes
emergencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already establish that this is a safe, read-only, idempotent, closed-world computation, so the safety profile is well covered. Beyond that, the description only hints at a two-step mechanic (reduce primary share, then draw on backup units) and says nothing about how the gap is computed, how percentage inputs interact with integer demand, or what a result looks like.

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 tightly-written sentence with no filler or redundancy. It is efficient, though the brevity comes at the cost of the missing detail noted in the other dimensions.

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?

This is a four-parameter, all-required computational tool with no output schema and no schema descriptions, so the description bears the full explanatory burden. It does not describe the computation, the expected return value, or how out-of-range or conflicting inputs (e.g., a delayed percentage combined with a large emergency quantity) are handled, leaving an agent unable to predict results.

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 must carry the load, but it only loosely maps to 'fraction' (primary share) and 'emergency' (backup units) and never mentions 'demand' or 'delayed'. The schema's own titles ('Net purchasing requirement', 'Primary share delayed (%)') do more work than the description, which adds no formula-level meaning to any parameter.

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 verb 'Model' plus a resource ('disruption to the primary share of an order') and a secondary action ('deduct additional units available from a backup source') give a rough idea that this is a calculation tool. However, it never states what quantity is produced or returned, and the phrase 'interruption gap' from the title is never explained, so an agent can only infer the output.

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?

No guidance on when this tool should be chosen, what scenario it applies to (supply-chain disruption? order fulfillment?), or when a sibling tool would be preferable. The agent has to guess from the name alone whether this is a modeling utility or a data lookup.

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.