Skip to main content
Glama

Estimate My Paycheck

Compare take-home pay in every state

compare_states
Read-onlyIdempotent

Take-home pay for the same salary in the 50 states and DC in 2026, sorted from the highest. Useful to answer "which state lets me keep the most" or to price a move.

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>"
    },
    "name": "compare_states"
  }
}

Input Schema

NameRequiredDescriptionDefault
salaryYesAnnual gross salary in dollars. Give this or hourly_rate.
tax_yearNoTax year, 2026 or 2027. Default: the year in force today (2026 now; 2027 from January 1, 2027).
k401_percentNoPre-tax 401(k) contribution, percent of gross. Default 0.
filing_statusNoDefault single.
pay_frequencyNoDefault biweekly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tax_year
      Added value: +{
      +  "description": "Tax year, 2026 or 2027. Default: the year in force today (2026 now; 2027 from January 1, 2027).",
      +  "example": 2026,
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and closed-world, so safety needs no restating. The description adds the comparison scope and the descending sort, which is useful, but says nothing about what the result looks like (all 51 entries? amounts, effective rates?) or how long it runs.

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?

Two sentences, zero filler, with the scope and ordering front-loaded before the use-case hint. Nothing could be cut without losing information.

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

Completeness4/5

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

For a five-parameter, single-required comparison tool with no output schema, the definition covers the input intent and the sort order well. The main gap is the return shape, which an agent must discover by calling, but annotations and full schema coverage keep that from being severe.

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 coverage is 100%, so all five parameters are documented in the schema itself; baseline 3 applies. The description adds only that one salary is applied uniformly across states, and its "in 2026" framing slightly undersells the tax_year parameter, which accepts 2027.

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?

Names a specific resource and operation: take-home pay comparison across the 50 states and DC, sorted descending. That is distinguishable from calculate_paycheck (single calculation) without needing the sibling's schema, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete use cases ("which state lets me keep the most", "price a move") that tell an agent when this tool is the right pick. It stops short of stating exclusions or pointing to calculate_paycheck for a single-state, single-salary figure.

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.

Resources