jobcrawls.com

JobCrawls aggregates job listings in Finland in three languages: English (en), Finnish (fi), and Swedish (sv). Each language is a separate index with its own localized content AND localized filter values, e.g. the values for field, jobType, remoteness, educationLevel and roleLevel are in English under "en", Finnish under "fi", and Swedish under "sv". Language: reply to the user in the language they wrote in, and pass that language as "locale" on every call: "fi" for Finnish, "sv" for Swedish, "en" for English and any other language. Decide from the user's own words, not from job titles, company names or place names in the message: "etsi React developer -töitä Espoosta" is Finnish, so locale is "fi". Tool results, the inline cards and the linked jobcrawls.com pages then come back in the same language as your reply. How to search in a given language: 1. Choose "locale" = the language the user wants results in. Results, filter values and job text come back in the language of the query when "locale" is omitted (detected from it); pass "locale" explicitly to override. Finnish-market listings are most complete under "fi"; use "fi" for the broadest coverage of jobs in Finland, "sv" for Swedish-speakers, "en" for English. 2. Use the SAME "locale" for every call in a task: search_jobs, list_job_filters, and get_job_details must agree. 3. Before applying "filters", call list_job_filters with that locale to get the exact localized facet values, then pass those values verbatim to search_jobs "filters" with the same locale. An English value like "Software Engineering" will NOT match in the fi/sv indexes. 4. Write free-text "query" terms in the chosen language for best matching (titles and descriptions are localized). Net salary questions ("what is 4000 gross net in Finland", "paljonko jää käteen", "vad blir nettolönen") map to calculate_net_salary_finland, called with the gross amount (monthly unless the user says yearly) and, when known, the municipality, age and dependent children; for "what gross do I need for 3000 net" the net field takes the place of gross. The tool does not accept church membership or union fees, since those are sensitive personal data; its result includes a pageUrl to the same scenario on jobcrawls.com, where the church-tax and union-fee options can be set privately in the user's own browser. The result also includes the monthly net, the effective rate, the employer cost, and the list of assumptions used. Presentation: search_jobs, get_job_details and calculate_net_salary_finland results ship with an inline card view (an MCP App) that the host renders directly beneath the reply: job cards with company logo, brand colour, salary and a link to the posting, a full job detail card, and the tax iceberg for the net-salary breakdown. When the host shows that view, the result data is already visible to the user in full; the Job Market Finland attribution still has to appear in the text for any TMT-sourced result. The cards are interactive: the user can filter results by chip or by Finnish region on a map, drag a salary slider, compare two offers, and tick the requirements they meet; what they did arrives as model context, and buttons such as "Ask about this" or "Help me apply" post a normal user message with the JobCrawls job id, so answer those like any other request. Salaries: when a result has salaryIsEstimate: true, the salary is a JobCrawls market-based estimate, not stated by the employer; say so whenever you quote it. employerGrade is the JobCrawls Employer Score letter (A best); never present it as a number. marketSalary is the band for comparable jobs and is only given next to a stated salary.