Skip to main content
Glama

Delivery Workload FTE

bpj_courier_workload_fte
Read-onlyIdempotent

Convert weekly workload to full-time equivalents after reserving non-delivery time and show whole-person headcount.

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": {
      "workload": "<workload>",
      "week": "<week>",
      "productive": "<productive>"
    },
    "name": "bpj_courier_workload_fte"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekYes
workloadYes
productiveYes

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?

The annotations already establish read-only, idempotent, non-destructive behavior, so safety is covered. The description adds genuine behavioral context by disclosing two computational traits: non-delivery time is reserved before conversion, and the result is rounded to whole-person headcount. It still says nothing about rounding direction, zero-workload handling, or result format.

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 sentence that front-loads the conversion, then qualifies it with the reservation step and the rounding outcome. No filler, no restatement of the name.

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 three-parameter pure calculation with no output schema, the description conveys the core formula and rounding behavior, which is the essential part. It leaves open the exact return shape (decimal FTE versus integer headcount, or both) and edge behavior such as near-zero productive share, so it is adequate but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the property titles are informative ('Standard full-time weekly hours', 'Workload hours per week', 'Share available for delivery (%)'). The description maps 'reserving non-delivery time' onto the productive-share parameter and clarifies that the output is whole-person headcount, adding meaning beyond the bare schema labels — though it doesn't pin down units for 'week' or the percent convention.

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 a concrete verb-and-resource pair: convert weekly workload hours into full-time equivalents, then round to whole-person headcount. That is specific enough to separate it from workload-adjacent siblings such as cycle-count or route time budget tools, though it never names an alternative explicitly.

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?

The phrase 'after reserving non-delivery time' implies the calculation's precondition, but there is no statement of when an agent should choose this tool over a sibling or what inputs must be gathered first. Usage is inferable from the arithmetic flow rather than stated.

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.