Panta Swiss Job Market Data

Read your experience bank

list_experience

Read-onlyIdempotent

List the connected user’s confirmed factual experience, with IDs and revisions for safe edits.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Results per page (1–50).
`offset`	No	Use next_offset from the previous response; maximum 5000.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds real value beyond that by disclosing that only 'confirmed factual' entries are returned and that records carry IDs and revisions — exactly what an agent needs before editing. It doesn't mention pagination behavior, but the schema covers that.

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?

One sentence, front-loaded with the verb and resource, with no redundant or filler wording. Every clause (confirmed, IDs, revisions, safe edits) carries information.

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?

A simple two-optional-parameter read tool with full annotations and complete schema coverage needs little more; the description still conveys return content (IDs, revisions) and result scope. Without an output schema, a brief note on ordering or result shape would have closed the last gap.

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%, with limit and offset both documented including the next_offset convention, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond that; baseline 3 applies.

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?

Names a specific verb and resource: listing the connected user's confirmed factual experience. The 'confirmed' qualifier and the mention of IDs and revisions make the scope concrete. It stops short of naming save_experience as the counterpart, so sibling differentiation is only implied.

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?

The phrase 'for safe edits' implies the intended follow-up (retrieve IDs/revisions before updating via save_experience), but it never states when to call this versus other list tools or any prerequisite. Usage is inferable rather than explicit.

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?