Skip to main content
Glama

Place profile: tax regime and residence route

place_profile
Read-onlyIdempotent

What Patrician.ch publishes on one place to live, or on up to 2 places in a country (with the names and pages of the others it covers there): the tax regime and any special regime for new residents (lump sum taxation, flat tax, non-dom rules), the residence route, income tax on $1M, cost of living (Zurich = 100), safety, schools, sun hours and the patrician.ch page.

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": {
      "place": "<place>"
    },
    "name": "place_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYesA city or a country, for example Zug, Dubai, Lake Como, Portugal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the coverage envelope (one place, or up to 2 per country, with names/pages of other covered places) and the exact content set returned, which the annotations cannot convey.

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?

It is a single front-loaded sentence with no filler, and the scope caveat is stated early. The dense comma-separated content list is efficient but borders on a data dump, which keeps it just short of exemplary.

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?

With no output schema, the description must carry the return-value burden, and it does so by enumerating every published field including the reference scale for cost of living (Zurich = 100) and the page URL. For a one-parameter read-only lookup, nothing an agent needs to call it correctly is missing.

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% and the single 'place' parameter already documents that a city or country is accepted with examples. The description's city-vs-country distinction and the 'up to 2 places' rule mostly describe return scope rather than adding new meaning to the parameter itself, so it sits at the high-coverage baseline.

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 uses a specific framing ('What Patrician.ch publishes on one place to live') and enumerates the resource contents: tax regime, special new-resident regimes, residence route, income tax on $1M, cost of living, safety, schools, sun hours, and the source page. That makes the tool's output distinguishable in substance from income_tax_by_place or passport_profile, 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for a per-place profile, and the 'up to 2 places in a country' clause hints at a coverage limit. There is no explicit when-to-use/when-not statement and no routing to compare_places or rank_places for multi-place work, leaving the agent to infer the boundary.

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