Skip to main content
Glama

Pick Wave Staffing

bpj_pick_wave_staffing
Read-onlyIdempotent

Translate a picking wave into labor-hours and the minimum whole pickers needed in the available window.

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": {
      "picks": "<picks>",
      "pace": "<pace>",
      "hours": "<hours>"
    },
    "name": "bpj_pick_wave_staffing"
  }
}

Input Schema

NameRequiredDescriptionDefault
paceYes
hoursYes
picksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuine behavioral value beyond that by disclosing the two computed outputs and the rounding behavior implied by 'minimum whole pickers'. It stops short of stating the exact formula or how the hours window caps the result.

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 with no filler; the resource and the two outputs are front-loaded so an agent can decide quickly. Nothing here could be trimmed without losing meaning.

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 three-parameter pure calculator with no output schema and full annotation coverage, the description is close to sufficient: it states what is produced and the whole-number rounding. The main remaining gap is that it never spells out the labor-hours relationship or how insufficient hours affects the picker count, which an agent might need to interpret results.

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 burden, and it only loosely maps its concepts ('picking wave', 'labor-hours', 'available window') onto the three parameters. The schema's own titles ('Lines picked per person-hour', 'Hours available for wave', 'Pick lines in wave') do most of the unit clarification, and edge cases like picks=0 or a zero-picker result are not addressed.

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 gives a concrete verb ('Translate') and resource ('a picking wave') and names both outputs: labor-hours and the minimum whole number of pickers. That is far more specific than a tautology, though it does not contrast itself with any sibling calculator (none of the listed siblings overlap, so differentiation is implicit rather than stated).

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 phrasing 'in the available window' and the required picks/pace/hours inputs, which sketch a staffing-planning scenario. There is no explicit when-to-use, when-not-to-use, or prerequisite guidance (e.g. that pace must be a positive rate, or what to do when picks exceed pace*hours).

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.