Skip to main content
Glama

decisions

by com.everydaybudd

Raise / Bonus True Value

raise_bonus_value
Read-onlyIdempotent

Raise / Bonus True Value — Shows how much of a raise or bonus you actually keep after marginal tax and lifestyle inflation. Returns a one-line verdict plus a link to the full interactive page with the numbers pre-filled. Accepts only numbers and enums.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoOne of: raise, bonus.
yearNoTax year, e.g. 2026. Omit to use the current tax year.
stateCodeYesTwo-letter US state code, e.g. CA, TX, NY.
raiseAmountYesA non-negative number (US dollars unless the field name says otherwise).
filingStatusYesOne of: single, married_joint, married_separate, head_of_household.
currentSalaryYesA non-negative number (US dollars unless the field name says otherwise).
annualInflationPercentNoPercentage from 0 to 100.
lifestyleInflationPercentNoPercentage from 0 to 100.

TDQS

A3.7/5.0
Behavior3/5

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

Annotations provide readOnlyHint and idempotentHint, so the description adds minimal behavioral context beyond stating it returns a one-line verdict and link. No contradictions with annotations.

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?

Three sentences with the purpose front-loaded. No wasted words; every sentence serves a purpose.

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?

While purpose is clear, the description lacks detail on the calculation (e.g., what 'marginal tax and lifestyle inflation' entail) and does not describe the return format beyond 'one-line verdict,' leaving the agent with incomplete context.

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% with clear parameter descriptions. The description adds 'accepts only numbers and enums,' which is already obvious from the schema, so no meaningful addition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool calculates the net value of a raise or bonus after tax and lifestyle inflation, using specific verbs ('shows') and a defined resource. It is distinct from siblings like job_offer_worth_it.

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?

The description implies usage for examining raise/bonus impact but lacks explicit when-to-use or when-not-to-use guidance, nor does it reference sibling tools as alternatives.

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

All decisions toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool targets a distinct financial decision (filing status, freelancer rate, job offer, raise/bonus, Roth vs Traditional), with no overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent pattern of descriptive snake_case phrases, clearly indicating the decision type.

Tool Count4/5

Five tools is a reasonable number for a decision-support server, covering common personal finance scenarios without being excessive or too thin.

Completeness3/5

While core decisions are covered, there are notable gaps such as mortgage vs. rent, debt payoff strategies, or investment comparisons, which limit completeness for the full domain.

Resources