Skip to main content
Glama

Overall Equipment Effectiveness

bpj_overall_equipment_effectiveness
Read-onlyIdempotent

Calculate availability, performance and quality from actual runtime, ideal cycle time and accepted output to obtain OEE.

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": {
      "planned": "<planned>",
      "run": "<run>",
      "ideal": "<ideal>",
      "total": "<total>",
      "good": "<good>"
    },
    "name": "bpj_overall_equipment_effectiveness"
  }
}

Input Schema

NameRequiredDescriptionDefault
runYes
goodYes
idealYes
totalYes
plannedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds the calculation's conceptual basis, but says nothing about output form (ratio vs percentage), division/validation behavior, or what happens with inconsistent inputs such as run > planned.

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 front-loaded sentence with the verb first and no filler. Every clause contributes to describing the calculation.

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?

For a five-required-parameter calculator with no output schema, the description should at minimum state the output form and the role of every input. It covers the concept but leaves two parameters and the return value unexplained, so an agent would need to supply its own domain knowledge.

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 it only loosely maps three concepts ('actual runtime', 'ideal cycle time', 'accepted output'). It never mentions the 'planned' or 'total' parameters, nor the formulas (availability = run/planned, performance = ideal×total/run, quality = good/total) that would tell an agent exactly how each value is used.

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 ('Calculate') and names both the derived metrics (availability, performance, quality) and the OEE result, plus the conceptual inputs. It is clearly distinguishable from the unrelated sibling calculators, though it never explicitly differentiates from them.

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 implied by the nature of a pure calculation: feed runtime, ideal cycle time and output to get OEE. There is no statement of preconditions (e.g. run must not exceed planned, good must not exceed total) and no guidance on when to prefer this over a manual or alternative calculation.

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.