Skip to main content
Glama
Sign In
shopfloor-mcp

shopfloor-mcp

by champion-buzz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

utilization_report

Read-onlyIdempotent

Calculate booked versus available hours per resource between two ISO dates, weekdays only, to assess capacity and identify utilization gaps.

Instructions

Booked vs. available hours per resource between two ISO dates (weekdays only).

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "utilization_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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, non-destructive, and closed-world, so the safety profile is covered. The description adds a genuine behavioral rule not in the annotations — 'weekdays only' — which materially changes result interpretation. It does not address timezone, partial-day handling, or whether dates are inclusive, so it stops short of a 4.

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 no filler; the metric, grouping dimension, and date constraint all arrive before any hedging. Nothing is redundant with the schema or annotations.

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 shape need not be explained, and annotations cover safety. Still, a two-required-parameter reporting tool with zero schema descriptions leaves an agent uncertain about endpoint inclusivity and scope (all resources vs. filtered) after reading the description.

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% — only titles 'Start Date'/'End Date' exist — so the description must carry the load. It does state ISO format and that the range is bounded, which is real added meaning, but it omits inclusivity of endpoints and how the range interacts with the weekday-only rule.

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 names the exact computation (booked vs. available hours per resource over a date range), which is specific enough to distinguish it from siblings like late_risk_report or find_next_slot. It is a noun phrase rather than a verb+resource statement, but the resource and metric are unambiguous.

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 guidance on when to call this instead of siblings such as late_risk_report, nor any stated preconditions (permissions, resource scope, whether ranges can span months). The agent must infer usage entirely from the phrase 'booked vs. available hours'.

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

Deploy Server

Other Tools