Skip to main content
Glama

New Hire Ramp Payback

bpj_new_hire_ramp_payback
Read-onlyIdempotent

Estimate when cumulative contribution covers onboarding and payroll using one ramp productivity level followed by full productivity.

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": {
      "induction": "<induction>",
      "full": "<full>",
      "loaded": "<loaded>",
      "ramp": "<ramp>",
      "rampMonths": "<rampMonths>"
    },
    "name": "bpj_new_hire_ramp_payback"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullYes
rampYes
loadedYes
inductionYes
rampMonthsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the computational model (ramp contribution first, then full productivity contribution, compared against cumulative onboarding and payroll cost), which is meaningful context. It does not disclose what the tool returns (a month count, a break-even table?) or what happens when payback never occurs, and no output schema fills that gap.

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 front-loaded sentence with no filler; the core comparison (cumulative contribution vs. onboarding and payroll) comes first. Some of its brevity shades into under-specification rather than economy, but nothing is redundant.

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?

This is a five-required-parameter quantitative model with no output schema and no per-parameter descriptions, so the definition should explain the return value and the modelling assumptions. It gives the high-level idea but not the output contract (break-even months? payback flag?) or cost/contribution treatment during ramp, leaving an agent unable to predict results confidently.

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% — parameters carry only titles, so the description must carry the semantic load. It maps loosely onto the inputs ('onboarding and payroll' suggests induction and loaded; 'one ramp productivity level followed by full productivity' suggests ramp, rampMonths, full), but leaves real ambiguities: whether the loaded monthly cost continues unchanged during the ramp, whether ramp (%) scales contribution only, and the time unit of 'full'.

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 states a specific verb ('estimate') and a specific outcome (when cumulative contribution covers onboarding plus payroll), and it names the model shape (one ramp level, then full productivity). An agent can distinguish this payback model from siblings like bpj_agency_hire_crossover or bpj_absence_cover_cost, though it never explicitly contrasts them.

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 only implied: the phrase 'one ramp productivity level followed by full productivity' signals this is the simplified two-phase model, so an agent can infer it applies to straightforward ramp/payback scenarios. There is no explicit when-to-use, no prerequisite statement, and no mention of cases where a more granular model would be preferred.

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.