CalcBright Calculators

Pay Raise Calculator

pay_raise_calculator

Read-onlyIdempotent

A 5% pay raise on $60,000 is $63,000 – only 1.25% more after 3.7% US inflation. See a raise per year, month and hour, what it is worth net and in the Gulf. Web page: https://calcbright.com/pay-raise-calculator

Input Schema

Name	Required	Description	Default
`hours`	No	Hours per week (hrs) Used to convert between hourly and annual pay (52 weeks)
`raise`	No	Raise (%)
`method`	No	Raise given as	percent
`newPay`	No	New annual salary
`current`	No	Current annual salary
`payType`	No	Pay is	annual
`currency`	No	Currency	USD
`inflation`	No	Inflation over the year (%) Optional – your country’s latest 12-month consumer price inflation. Shows what the raise is worth after rising prices.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / inflation

Added value: +{
+  "description": "Inflation over the year (%) Optional – your country’s latest 12-month consumer price inflation. Shows what the raise is worth after rising prices.",
+  "maximum": 1000,
+  "minimum": -50,
+  "type": "number"
+}

Changed1 schema field changedOct 16, 2026
- addedInput schema / properties / newPay / default
```
Added value: +63000
```
First observedOct 12, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is already covered. The description adds a concrete numeric example and mentions output dimensions (year/month/hour, net, Gulf) but does not disclose limits, rounding, or how the 'Gulf' comparison works.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is two sentences and includes a useful concrete example, but it leads with the example rather than stating the tool’s purpose, and the web page URL is promotional rather than operational. Nothing is verbose, but the structure is not optimally front-loaded.

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?

With eight optional parameters, no output schema, and annotations covering read-only/idempotent behavior, the description does enough to indicate the calculation’s scope. However, it leaves unclear how method, payType, and newPay/raise interact, and the 'net and in the Gulf' claim is not elaborated.

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 100%, so all eight parameters are documented in the schema. The description adds only an example using default-like values and does not clarify interactions such as method versus raise/newPay or payType behavior, so baseline 3 is appropriate.

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 makes clear this tool computes pay raise outcomes, listing outputs like per year/month/hour, net worth, and Gulf context. It does not explicitly differentiate itself from siblings such as salary_calculator or inflation_calculator, but the resource is unambiguous.

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 guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description is purely illustrative and does not tell an agent how to decide between this and sibling calculators.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CalcBright Calculators tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?