Skip to main content
Glama

Cycle Count Workload

bpj_cycle_count_workload
Read-onlyIdempotent

Translate two SKU groups and annual count frequencies into yearly count lines and daily workload.

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": {
      "fast": "<fast>",
      "fastFreq": "<fastFreq>",
      "slow": "<slow>",
      "slowFreq": "<slowFreq>",
      "days": "<days>"
    },
    "name": "bpj_cycle_count_workload"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
fastYes
slowYes
fastFreqYes
slowFreqYes

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, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that it converts inputs into two computed quantities, which is useful context beyond the annotations, but it says nothing about the calculation method, units, rounding, or output shape. For a pure calculator that is an acceptable but not rich disclosure.

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?

One sentence, front-loaded with the transformation and free of filler. It is efficient, though for a five-parameter calculator the brevity leaves gaps that a slightly longer sentence could have closed.

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?

With five required parameters, no output schema, and zero schema descriptions, the definition should explain at least what the returned 'yearly count lines' and 'daily workload' look like or how 'days' feeds in. It is adequate for an agent to attempt a call but incomplete for interpreting or trusting the result.

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 this description must carry the parameter burden. It does map 'two SKU groups' to fast/slow and 'annual count frequencies' to fastFreq/slowFreq, but it never mentions the required 'days' (working days per year) parameter, and the schema supplies only titles. Partial compensation for a low-coverage schema.

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 uses a specific verb ('Translate') and names both the inputs (two SKU groups, annual count frequencies) and the outputs (yearly count lines, daily workload), so an agent knows this is a cycle-count workload calculator. It is not explicitly differentiated from siblings, but none of the listed siblings perform this calculation, so the risk of mis-selection is low.

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 stated preconditions, and no pointer to an alternative tool. The agent must infer the use case entirely from the tool name and the sentence about translating inputs into outputs.

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.