Panta Swiss Job Market Data

Save reusable experience

save_experience

Destructive

Create or revise a confirmed historical experience. Goals belong in update_workspace_profile.preferences. Use only facts the user supplied. Editing requires id and the current revision; preserves prior wording in version 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": {
      "kind": "<kind>",
      "title": "<title>",
      "text": "<text>"
    },
    "name": "save_experience"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No
`kind`	Yes
`text`	Yes
`title`	Yes
`revision`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent writes; the description adds genuinely new behavior — that editing is revision-guarded and prior wording is preserved in version history, which materially softens the destructive framing. It doesn't state what happens on a revision mismatch or whether omitted fields are cleared, keeping it below a 5.

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, each doing distinct work: purpose, exclusion/alternative, and edit precondition plus side effect. Front-loaded with the operation and contains no filler or repetition of schema constraints.

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 5-parameter mutation tool with no output schema, it supplies the destination routing, the grounding constraint ('only facts the user supplied'), and the optimistic-concurrency rule. The main remaining gap is failure behavior on revision conflict and confirmation state requirements for what counts as 'confirmed'.

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 0%, so the description must carry semantics: it explains that `id` and `revision` are the editing pair and that `revision` must be current, which is real added meaning. But `kind`, `title`, and `text` get no semantic treatment, and the create-vs-edit parameter dependency (id/revision supplied together) is only implied.

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?

States a specific verb pair (create or revise) and resource (confirmed historical experience), and explicitly names the sibling `update_workspace_profile.preferences` as the wrong destination for goals. It's clear what the tool does, though 'experience' as a record type is only inferable from the sibling `list_experience`.

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?

Gives two concrete usage rules: goals go to update_workspace_profile.preferences, and editing requires id plus the current revision. Missing an explicit statement of when not to use it (e.g. unconfirmed/uncertain facts), but the routing guidance is strong for a small toolset.

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?