Panta Swiss Job Market Data

Save a job decision

save_job

Destructive

Save an indexed active job as interested, dismissed or new in the connected user’s workspace. Rechecks the index and preserves source evidence. Does not apply to the job.

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": {
      "job_id": "<job_id>"
    },
    "name": "save_job"
  }
}

Input Schema

Name	Required	Description	Default
`canton`	No	Use matched_location.canton from the selected search result to preserve its supporting worksite and source links.
`job_id`	Yes
`decision`	No		interested

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already disclose that this is a non-read-only, destructive, non-idempotent mutation. The description adds useful context by saying it rechecks the index and preserves source evidence, but it does not explain what the destructive behavior means or what happens to existing decisions.

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?

The description is short and front-loaded with the core action. The final sentence is useful but slightly ambiguous because 'does not apply to the job' could be clearer.

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?

For a three-parameter mutation with a destructive annotation and no output schema, the description is adequate to identify the action but incomplete about mutation consequences and return behavior. It covers the recheck and evidence-preservation aspects but leaves key operational details implicit.

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 only 33%, so the description must compensate. It clarifies that the job is indexed and lists the decision values, but it does not explain the required job_id or how to obtain it beyond the vague phrase 'indexed active job'.

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 gives a specific verb and resource: saving an indexed active job with one of three decisions. It also distinguishes the tool from applying to the job, though it does not name save_application or other siblings 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 implied by recording a job decision, and the final sentence excludes applying to the job. However, it does not explicitly say when to use this versus save_application or list_saved_jobs.

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?