Skip to main content
Glama
tresor4k

macalc

calculate_salary_comparison_ppp

Compare salaries across countries using purchasing power parity (PPP). Input your salary and select source and target countries from FR, US, UK, DE, CH, BE to get the equivalent salary adjusted for cost of living.

Instructions

Compare salaries across countries using PPP (FR=0.79, US=1.0, UK=0.81, DE=0.77, CH=1.36, BE=0.80). Returns: {ppp_from, ppp_to, equivalent, ratio}. See list_bundles for related 'vie-quotidienne' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
salaryYesSalary in local currency
from_countryYesSource country
to_countryYesTarget country

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

With no annotations, the description provides some behavioral insight by explaining the calculation's purpose and return structure. However, it does not disclose whether the tool is read-only, any side effects, or authentication needs, which would be expected for a calculation tool.

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 extremely concise—a single sentence plus a list of factors and a reference to related tools. Every element is informative and non-redundant, and the PPP factors are efficiently presented.

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?

Given the simple schema (3 enums) and no output schema, the description adequately covers the tool's purpose, input, and output format. The mention of related bundles adds context. However, it could be slightly more explicit about the calculation method (e.g., multiplying by ratio).

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?

The schema already describes parameters fully (100% coverage), but the description adds significant value by providing the PPP factors for each country and the return object shape, which helps the agent understand the calculation context beyond raw schema.

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 clearly states 'Compare salaries across countries using PPP' and lists the specific countries and their PPP factors, which distinguishes it from other calculation tools. The verb 'compare' and resource 'salaries' are specific, and listing PPP factors adds specificity.

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?

The description provides PPP factors and mentions related calculators via list_bundles, giving context for when to use this tool for cross-country comparison. However, it does not explicitly state when not to use it or list alternatives, leaving some ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server