Skip to main content
Glama

Merit Raise Budget

bpj_merit_raise_budget
Read-onlyIdempotent

Apply a merit increase to eligible base payroll and prorate the incremental cash expense over effective months.

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": {
      "salary": "<salary>",
      "eligible": "<eligible>",
      "raise": "<raise>",
      "months": "<months>"
    },
    "name": "bpj_merit_raise_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
raiseYes
monthsYes
salaryYes
eligibleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so safety behavior is covered. The description adds that the tool computes a prorated incremental expense, but it does not disclose output form, rounding, currency assumptions, or whether the result is annualized or partial-year.

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?

The definition is one tightly written sentence with no wasted wording, and the core calculation is front-loaded. It communicates the tool's operation without filler.

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 four-parameter calculation tool with no output schema, the description covers the core computation but omits the expected return value, rounding, and any assumptions about the result. It is adequate to identify the tool but not fully complete for calling and interpreting it confidently.

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 parameter meaning. It conceptually maps all four inputs: salary, eligible share, raise, and effective months, and it implies the proration relationship. However, it does not state the formula, units, or rounding behavior explicitly.

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 calculation: applying a merit increase to eligible base payroll and prorating the incremental expense over effective months. This is clearer than a generic budget tool, though it does not explicitly distinguish itself from similarly named budget siblings such as proportional budget or campaign budgeting.

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?

The description provides no when-to-use guidance, exclusions, or alternatives. It describes the calculation but leaves the agent to infer the appropriate context from the tool name and sibling set.

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.