Skip to main content
Glama

Weekly Overtime Pay

bpj_weekly_overtime_pay
Read-onlyIdempotent

Split weekly pay into regular and overtime hours using the threshold and premium multiplier supplied by the caller.

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": {
      "actual": "<actual>",
      "threshold": "<threshold>",
      "rate": "<rate>",
      "factor": "<factor>"
    },
    "name": "bpj_weekly_overtime_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateYes
actualYes
factorYes
thresholdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds that the operation is a regular/overtime split, but it does not disclose rounding behavior, edge cases, or the shape of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no filler. It is concise and readable, though it is too terse to carry much operational detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter calculation with no output schema and no schema descriptions, the definition is incomplete. It states the core split but omits how inputs are interpreted, how results are formatted, and how boundary cases are handled.

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 compensate for the four required inputs. It mentions only the threshold and premium multiplier, and does not clarify the meaning or interaction of 'actual' and 'rate' or the calculation formula.

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 specific verb and resource: it splits weekly pay into regular and overtime hours. It is not tautological, but it does not distinguish this tool from any sibling alternative.

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 explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative. The weekly overtime context is only implied by the name, title, and description.

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.