Skip to main content
Glama

Suggest cities for me

suggest_cities
Read-onlyIdempotent

Rank all published cities by the current profile: top five not already in cities, with their two biggest observed score contributions. Same inputs as compare_cities; cities may be empty. Fixed scoring by default; Weather uses your nice-day definition. Missing lines do not count there: check coverage before deciding.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "suggest_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyNoScore only these criteria; every other line gets weight 0 (each listed one keeps its `weights` value, else 100). For a one-line question: only ["nice_days"] with comfort {min:20,max:28}
workNoThe person's kind of work, only if they said it: software (Software and IT), engineering (Engineering, not software), science (Research and science), medicine (Doctors and dentists), nursing (Nursing and care), teaching (Teaching and education), finance (Finance and accounting), law (Law), marketing (Marketing, design and media), office (Office and administration), sales (Sales and retail), hospitality (Hospitality and food), trades (Construction and trades), transport (Transport and logistics), public (Public sector), management (Management), founder (Founding a company). Adds what people in that work earn there and how many jobs its field holds to Work and ambition, and shares the group's weight by the kind's recipe (founder: young companies, developers, graduates); each city then says why in plain sentences (work). Leave out for the same Work and ambition as everyone
limitNoHow many ranked cities to describe in the summary (default 10); the ranking counts the rest
citiesNoAlready chosen cities to exclude, if any
detailNo"summary" (default): verdict, ranking, weighted lines with citations, money in brief, who can move there, notes, required unknowns and next inputs. "full": every line, tax line and source, for programs
presetNoStarting weights
salaryNoYour gross yearly salary, the same everywhere
comfortNoWeather: what a nice day is, for criterion nice_days: the daytime temperature range, °C (default 18-30 on the feels-like temperature; basis "air" uses the air in the shade), then the tests a day must pass. Only the person's own words: rain and sky are on unless they drop them; humidity, wind and daylight only when they ask. All from ERA5 (Open-Meteo, CC BY 4.0) and the latitude
housingNo
missingNoIn fixed scoring, missing lines do not count for that city. Only with opt-in relative scoring: lowest scores gaps at the lowest compared score, worst at 0, skip drops the line for all. Money is never imputed
pensionNoShare of your gross paid into a pension, 0.05 = 5%: it leaves take-home pay and is shown as saving, not cost. Tax relief is modelled for CA (RRSP), CH (pillar 3a), CZ (pension savings (penzijní spoření)), DE (occupational pension (Entgeltumwandlung)), EE (third pillar), ES (plan de pensiones), FR (PER (plan d'épargne retraite)), GB (workplace or personal pension), HU (voluntary pension fund), IE (occupational pension or PRSA), IT (fondo pensione), JP (iDeCo), NL (workplace pension), NO (IPS (individual pension savings)), PT (PPR), SG (SRS), US (401(k)); elsewhere it is not modelled and the share is counted as saving with no relief (each city's money says which)
regimesNoNewcomer tax regime per country, ISO alpha-2 -> regime id from list_metrics_and_sources. None counts unless named here; a named one is a scenario until the person's facts and confirmations meet every condition
savingsNoSavings in the display currency, for runway
stancesNoWhere the person stands on the position lines, which score a place by its distance from them: politics 0 (left) to 10 (right); abortion 0 not allowed or only to save her life, 1 also for her health or after rape, 2 also on social or economic grounds, 3 on request in the first weeks only, 4 on request to 10 weeks or later; couples_law 0 criminalised (same-sex relations a crime), 1 legal with no union in law, 2 civil union or partnership, 3 marriage. Pass only what the person told you or what you know they hold; never guess. A stance counts once its line has a weight (they are 0 by default)
weightsNoWeight 0-100 per criterion, on top of the preset. Criteria: money_left, living_cost, right_to_live, nice_days, winter_light, sunshine, dry_days, clean_air, safety, long_life, health_costs, childcare, family_leave, happiness, builders, field_pay, field_jobs, young_companies, time_zone, flight_home, airport, public_transport, rail, short_commute, cycling, walkable, active_commute, way_out, sea, mountains, green, internet, english, international, doctors, jobs, degrees, developers, qol, clean_government, politics, abortion, couples_law, founders_run, coworking, climbing, swimming, beach, run_ride, muggy, grey, hot_nights, heat, snow, wind
childrenNoChildren's ages: childcare after public support for under-6s (OECD), child credits and allowances where the tax uses them, health for each person
personalNoYour own 1-5 lines, scores keyed by city
spendingNoMonthly spending on everything except housing, childcare and health, which are counted separately
householdNoEveryone moving, you first. Anyone after you can bring their own pay; a spouse counts for joint filing even with none
normaliseNoDefault absolute: fixed city-local scores. Relative is opt-in: adding cities can change other scores, gap handling and the shared money basis.
overridesNoYour own numbers: city -> metric id -> value; money in the city's currency. health_premium is the household's premium a month (prefer healthPremium, which takes the period); childcare_cost is the household's own childcare a month (prefer childcareCost); childcare_net_couple_1 and similar replace the OECD reference figure, a year
taxTweaksNoPer-country tax tweaks keyed by ISO alpha-2
dealBreakersNoMust-pass criterion ids, e.g. right_to_live, money_left: a city fails, passes, or is unknown (no figure, no passport or other right given); unknown ranks after every city that passes
salaryByCityNoGross yearly salary per city (offers or estimates), keyed by city id or name
childcareCostNoWhat the household actually pays for childcare in a city, after support, keyed by city id or name, in the city's currency, with per "month" or "year": replaces the OECD reference figure
healthPremiumNoThe household's health insurance premium bought outside pay (US, CH, NL), keyed by city id or name, in the city's currency, with per "month" or "year" (a year is counted as a twelfth a month)
paidChildcareNoWhether the household pays for childcare for its children under 6 (default true). false: no childcare cost is counted. Ask when it matters: the default prices full-time care for an OECD reference household
displayCurrencyNoCurrency to show amounts in (default: the salary's, else EUR)

Output Schema

NameRequiredDescriptionDefault
reportVersionYesThe report's shape version (now 2.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: fixed scoring is the default with relative scoring as an opt-in, missing lines simply do not count, and a warning to check coverage before deciding. It does not explain pagination-free top-N behaviour or the cost of a large candidate set, which keeps it below 5.

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

Conciseness4/5

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

The core behaviour is front-loaded in the first clause and every sentence carries operational content. However, "top five not already in cities" conflicts with the `limit` parameter, which documents a default of 10, and "Weather uses your nice-day definition" largely duplicates the `comfort` schema description — both cost clarity.

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?

An output schema exists and annotations are rich, so the remaining burden is mostly behavioural, which the description partly meets. But for a 28-parameter tool it leans on "same inputs as compare_cities" — a cross-tool assumption the agent may not be able to verify — and leaves the five-versus-ten count ambiguity unresolved. A careful agent could still call it right, but only after reconciling the conflict.

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 96%, so the schema already documents all 28 parameters in depth and baseline is 3. The description's parameter-adjacent content ("cities may be empty," "missing lines do not count") restates what `cities` and `missing` already say in the schema. It adds nothing about the high-leverage parameters (weights, preset, dealBreakers) that an agent would need to reason about here.

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 opens with a specific verb and resource: "Rank all published cities by the current profile," and adds the output shape (top five, two biggest score contributions) plus the exclusion rule ("not already in cities"). That separates it from compare_cities, which presumably ranks a caller-supplied set. It falls short of 5 because the sibling differentiation is only implied by "cities may be empty" and it never names compare_cities or search_cities as the alternative to choose.

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?

"Same inputs as compare_cities; cities may be empty" implies this is the discovery entry point when the user has no city list yet, and "check coverage before deciding" gives one pre-call check. But there is no explicit "use this instead of X when…" statement, and the relationship to search_cities is left entirely to inference. A 3 reflects usable but inferred guidance.

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.