factory-floor-mcp

Overview Schema Source Related Servers Discussions Admin

production_kpis

Read-only

Retrieve a period-over-period management summary of factory performance for a date range, covering OEE, good/scrap parts, downtime reasons, delivery, late orders, and inventory alerts.

Instructions

Management summary for a period, compared with the previous period of the same length: OEE and its three factors, good and scrap parts, unplanned downtime hours with the top reasons, on-time delivery, open late orders and materials below reorder point.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "production_kpis"
  }
}

Input Schema

Name	Required	Description	Default
`date_to`	No	ISO date YYYY-MM-DD
`date_from`	No	ISO date YYYY-MM-DD

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered, and the description adds a genuinely useful behavioral trait not in the structured data: results are compared against the previous period of the same length. It does not mention default/omitted date behavior or any rate/permission constraints, keeping it short of a 5.

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 dense sentence, front-loaded with 'Management summary for a period,' with no wasted words. The metric list is long but each item earns its place by scoping the result set. Slightly list-heavy but efficient.

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?

An output schema exists, so return values need not be explained, and annotations cover the read-only nature. The gap is that both parameters default to null and the description never states what period is used when dates are omitted, which an agent needs to call it correctly.

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 100% and both parameters are documented in the schema, so the baseline is 3. The description adds no detail about date formatting, defaults, or what period is assumed when the nullable dates are omitted.

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 clearly identifies this as a rolled-up management summary spanning OEE, quality, downtime, delivery and inventory — a specific composite resource. However, it never names the overlapping siblings (machine_oee, downtime_pareto, scrap_summary, late_work_orders) to explain how it differs from them. A clear purpose, but no explicit sibling differentiation.

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 and no mention of alternatives, despite four sibling tools covering overlapping metrics. The agent must infer on its own whether to call this composite summary or the individual metric tools. Only implied usage is present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server