Skip to main content
Glama

Compare 2 places side by side

compare_places
Read-onlyIdempotent

Compares 2 places to live on one person's profile: income tax, net income, what they keep, exit tax, wealth tax, residence route, cost of living, safety, schools and sun, each with its patrician.ch page and the Patrician.ch head to head page where one exists. Use it for "Dubai vs Monaco", "Zug or Lugano" and other X vs Y questions.

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": {
      "places": "<places>"
    },
    "name": "compare_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
placesYes
childrenNo
householdNo
passportsNoPassports the person holds: eu (any EU country), uk, us, ch, ae, ca, au, sg, jp, il, or other.
current_homeNo
annual_income_usdNo
employment_incomeNoTreat the income as one person's salary and add the employee's compulsory social contributions where Patrician.ch models them. Default false.
liquidity_event_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing the return shape: each dimension arrives with its patrician.ch page plus a head-to-head page where one exists, and that results are scoped to a single person's profile. It still says nothing about authentication, query cost, or what happens when a head-to-head page is absent.

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?

Front-loaded with the core action, then the dimension list, then a usage sentence - a sensible order with no filler. The dimension enumeration is long but earns its place by telling the agent what the comparison returns in a tool with no output schema.

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?

For an 8-parameter, no-output-schema tool, the description does the essential job of explaining what comes back and when to use it. The unresolved gap is the input side: five parameters, including household composition and liquidity event, are left for the agent to guess at from their names alone.

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

Parameters2/5

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

Schema description coverage is only 25%: just passports and employment_income are documented in the schema, leaving children, household, current_home, annual_income_usd and liquidity_event_usd unexplained. The description's only hint is 'on one person's profile,' which gestures at the profile inputs without clarifying any of them, so it fails to compensate for the coverage gap.

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?

Specific verb and resource: "Compares 2 places to live on one person's profile," followed by an enumeration of the comparison dimensions (income tax, net income, exit tax, cost of living, safety, schools). The cardinality constraint "2 places" implicitly separates it from rank_places and place_profile, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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 explicit trigger guidance: 'Use it for "Dubai vs Monaco", "Zug or Lugano" and other X vs Y questions,' which is concrete and easy for an agent to pattern-match on. It stops short of exclusions or naming when to reach for income_tax_by_place or rank_places instead, which is the missing piece for a 5.

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