Skip to main content
Glama

Panta Swiss Job Market Data

Get an employer’s active and past Swiss jobs

get_company_jobs
Read-onlyIdempotent

Exact employer identity, active Swiss jobs or past jobs, source health and last checked dates. Past listings are not a complete hiring history.

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": {
      "id": "<id>"
    },
    "name": "get_company_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOpaque ID returned by search. URL-encode when used in an HTTP path.
limitNoResults per page (1–50).
offsetNoUse next_offset from the previous response; maximum 5000.
statusNoActive Swiss jobs from enabled sources, or separate inactive Swiss jobs; not a complete hiring history.active

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral disclosure: past listings are incomplete, which stops an agent treating results as a full hiring history, and it flags that source health and last-checked dates come back with the data. It says nothing about pagination behavior or what happens for an unknown employer ID, which matters given openWorldHint=true.

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?

Very short and the most load-bearing fact (past listings are incomplete) is placed last, which is slightly suboptimal, and the first sentence is a fragment with no verb. There is no filler, however, so the length is appropriate for the tool's simplicity.

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?

With no output schema, the description bears some responsibility for describing return values; it partially does so by naming employer identity, jobs, source health and last-checked dates. Combined with fully documented parameters and read-only annotations, an agent can call this correctly, but the description omits result/pagination shape hints and any mention of the total/next_offset pattern defined in the schema.

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 description coverage is 100%, including the crucial note that id is an opaque ID from search, so the schema carries the parameter burden. The description's 'active Swiss jobs or past jobs' loosely mirrors the status enum and reinforces that the two statuses are separate result sets, but it adds no syntax, defaults or pagination semantics beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (an employer's active and past Swiss jobs) and hints at extra return data (source health, last checked dates), but it is a verbless comma-spliced noun phrase rather than a statement of what the tool does. It never distinguishes itself from get_company or search_jobs, so an agent must infer that this is the per-employer job listing endpoint.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives such as get_company (identity only) or search_jobs (cross-employer search). The only caveat, 'Past listings are not a complete hiring history,' is a data-quality warning rather than guidance on when to select this tool or which status to request.

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