Skip to main content
Glama

Customer Demand Takt

bpj_customer_demand_takt
Read-onlyIdempotent

Translate demand per shift and net production minutes into takt seconds per unit and required hourly output.

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": {
      "shift": "<shift>",
      "demand": "<demand>"
    },
    "name": "bpj_customer_demand_takt"
  }
}

Input Schema

NameRequiredDescriptionDefault
shiftYes
demandYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the substantive point that this is a pure deterministic conversion and names both outputs, since there is no output schema. It does not disclose rounding/precision, units of the hourly figure, or behavior around the declared min/max bounds.

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?

One sentence, front-loaded with the computation, zero filler or repetition of the tool name. Every clause (inputs, outputs) earns its place.

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 two-parameter deterministic calculator with rich annotations, the definition covers inputs and both outputs, which is the essential information given there is no output schema. The only gap is precision/rounding and the exact derivation of hourly output, which is minor for this tool class.

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 must carry the parameter burden; it does partly by clarifying that "shift" means net production minutes available and "demand" means units required per shift, which is more than the bare titles convey. However, it doesn't explain the distinction between gross and net minutes, or unit expectations for the shift value, which is the main ambiguity a caller would face.

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?

States a specific verb ("Translate") plus the exact input quantities (demand per shift, net production minutes) and the two derived outputs (takt seconds per unit, required hourly output). The resource and computation are unambiguous. It does not name or contrast any sibling, though the sibling names are unrelated calculators, so confusion risk 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use statement, no exclusions, and no named alternatives. Applicability is only implied by the inputs named — an agent can infer this is the takt-time/line-balancing calculator, but nothing states when another tool (e.g. a capacity or battery-runtime calculator) would be preferred.

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.