Skip to main content
Glama

Cost of living

transita_cost_of_living
Read-onlyIdempotent

Monthly budget and rent ranges in US dollars for the cities Transita profiles, filtered by country or city. Figures are editorial estimates from public sources, each with its review date and sources. Use them for orientation, then check local listings.

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": "transita_cost_of_living"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name or slug, e.g. 'Berlin' or 'new-york'.
countryNoLowercase destination country code, e.g. 'de', 'ca' or 'uk'. 'gb' also works for the UK.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive, and closed-world nature of the tool. The description adds meaningful context beyond annotations by stating that figures are editorial estimates from public sources, include review dates and sources, and are not authoritative for decision-making.

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 description is three sentences with no waste. It front-loads what the tool returns, then adds provenance and a practical caveat.

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

Completeness5/5

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

For a simple read-only lookup with two optional, fully documented parameters and no output schema, the description is complete enough to call the tool correctly. It explains the returned data, filtering options, provenance, and the intended caution about using estimates.

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 the input schema already documents both parameters, including examples for city and country codes. The description reinforces that filtering is by country or city but does not add syntax or format details beyond what the schema provides.

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 states a specific resource: monthly budget and rent ranges in US dollars for cities Transita profiles. It explicitly names the filtering dimensions, country or city, which distinguishes it from the visa-focused sibling tools.

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?

It gives clear usage context: figures are for orientation and should be checked against local listings. However, it does not explicitly state when not to use this tool or name a direct alternative.

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.