Skip to main content
Glama

Kultranz: US Salary, Tax & Cost of Living

Compare two US metros

compare_cost_of_living
Read-onlyIdempotent

Compare the cost of living between two US metro areas and return the equivalent salary — the income needed in the second city to hold the same purchasing power. Uses BEA Regional Price Parities where the US average is 100. Answers 'is X more expensive than Y' and 'what salary do I need in Y to match X'. Call list_metros first if unsure of a city name.

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": {
      "fromCity": "<fromCity>",
      "toCity": "<toCity>"
    },
    "name": "compare_cost_of_living"
  }
}

Input Schema

NameRequiredDescriptionDefault
salaryNoSalary in USD to convert. Defaults to 100000.
toCityYesDestination metro, e.g. "San Francisco, CA" or just "San Francisco"
fromCityYesOrigin metro, e.g. "Austin, TX" or just "Austin"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds real value by naming the data source and its scale ('BEA Regional Price Parities where the US average is 100'), which tells the agent what the numbers mean and how they can be interpreted, though it stops short of describing precision, coverage gaps, or rounding.

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 core operation and its output are front-loaded in the first sentence, followed by the data source, the motivating questions, and the prerequisite hint. Every sentence is load-bearing and there is no redundant restatement of the schema.

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?

With no output schema, the description carries the burden of explaining return values and it does identify the key return ('the equivalent salary') plus the index basis. It does not specify whether per-city index values or the parity ratio are also returned, leaving a small gap for a tool whose output shape is undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the parameter baseline is 3, but the description adds interpretation beyond the schema by defining the direction of conversion ('income needed in the second city to hold the same purchasing power') and anchoring the index base at 100. That ≥> what the field-level descriptions convey, though it does not add format examples for city strings.

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 gives a specific verb and resource ('Compare the cost of living between two US metro areas') and states the concrete output ('return the equivalent salary'). It is clearly distinguishable from siblings like list_metros or get_take_home_pay without opening either schema.

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

Usage Guidelines5/5

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

It names the user questions it answers ('is X more expensive than Y', 'what salary do I need in Y to match X'), which disambiguates the use case, and it explicitly routes the agent to list_metros as a prerequisite when a city name is uncertain ('Call list_metros first if unsure of a city name').

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.