Panta Swiss Job Market Data

Find employers

search_companies

Read-onlyIdempotent

Search indexed employers. Headquarters and active_jobs do not prove Swiss vacancies. Use search_jobs to find Swiss positions.

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

Input Schema

Name	Required	Description
`q`	No	Employer keywords. Maximum 120 UTF-8 bytes.
`limit`	No	Results per page (1–50).
`offset`	No	Use next_offset from the previous response; maximum 5000.
`sector`	No	Sector contains this text. Maximum 40 UTF-8 bytes.
`country`	No	Headquarters country code, e.g. CH. This is not job location.
`has_jobs`	No	Filter on canonical active job count; not restricted to Swiss or fresh sources.
`swiss_jobs`	No	When true, only employers with a recorded domain and active Swiss-eligible jobs from enabled sources. Does not imply source freshness.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine value beyond that by disclosing that results come from an index and that certain fields are unreliable proxies for Swiss presence. It does not address result shape or freshness handling beyond the swiss_jobs caveat.

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?

Three short sentences, zero filler. Purpose is front-loaded, the caveat follows, and the alternative is named last — a clean decision-support ordering.

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?

For a 7-parameter filter-only search with no output schema, the description covers purpose, the sibling choice, and the main semantic pitfall well. It is slightly thin on what an employer record contains, though annotations and schema carry the rest adequately.

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%, including the crucial clarifications that country is headquarters not job location and that has_jobs is not Swiss- or freshness-restricted. The description's mentions of headquarters and active_jobs largely restate what the schema already documents, so baseline 3 applies.

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?

States a specific verb and resource ("Search indexed employers") and immediately distinguishes itself from the sibling search_jobs by naming it. An agent can tell which search surface to reach for without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent: use search_jobs for Swiss positions, i.e. do not use this tool to find Swiss vacancies. It also flags the interpretive trap (headquarters and active_jobs do not prove Swiss vacancies), which is precisely the when-to-use boundary an agent needs.

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

All Panta Swiss Job Market Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?