Skip to main content
Glama

On-Time In-Full Orders

bpj_on_time_in_full_orders
Read-onlyIdempotent

Deduplicate late and short orders using their overlap to count orders delivered both on time and in full.

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": {
      "orders": "<orders>",
      "late": "<late>",
      "short": "<short>",
      "both": "<both>"
    },
    "name": "bpj_on_time_in_full_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
bothYes
lateYes
shortYes
ordersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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, so the safety profile is covered. The description adds real value by disclosing the computational method (overlap deduplication via inclusion-exclusion), but omits what happens with inconsistent inputs (e.g. both greater than late or short) and says nothing about the response shape.

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 counting operation leads and the qualifier follows. Dense but every clause carries information.

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?

It is a pure arithmetic calculator with complete annotations and no output schema, so the burden is modest, and the one-sentence formula explanation is largely sufficient. The gap is the absence of any note on input consistency or on the returned value being a derived count.

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 parameter meaning and does not. The phrase 'using their overlap' obliquely signals that 'both' is the late-and-short intersection, but the other three parameters and the implicit constraints between them (precedence, non-negative result) are left entirely to the schema titles.

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?

Names a concrete operation (deduplicate overlapping sets and count) on a concrete resource (orders on time and in full). The purpose is unmistakable for a KPI calculator, though it makes no attempt to position itself against the unrelated sibling calculators.

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?

Says what is computed but gives no when-to-use, when-not-to-use, prerequisites, or any pointer to an alternative. Nothing tells the agent in what scenario this inclusion-exclusion count is the right call versus a plain total-orders tool.

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.