Skip to main content
Glama

Job Clerk

Stellenanzeige lesen

lese_stellenanzeige
Read-onlyIdempotent

Liest eine Anzeige anhand ihrer publicId: Arbeitgebertext, Vergütung, Berufserlaubnis-Belege und Quellen. Arbeitgeberweite Hinweise sind keine Zusage für diese Stelle. Liest nur öffentliche Daten, führt keine Bewerbung aus.

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": {
      "publicId": "<publicId>"
    },
    "name": "lese_stellenanzeige"
  }
}

Input Schema

NameRequiredDescriptionDefault
publicIdYespublicId aus der Suche oder dem letzten Abschnitt einer kanonischen Stellen-URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real value: it warns that employer-wide statements are not a commitment for this specific position, which is an interpretation caveat found nowhere in structured data. "Liest nur öffentliche Daten" partly restates readOnly but usefully scopes which data is reachable. Missing: behavior on an unknown or malformed publicId.

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 dense sentences, front-loaded with the verb, the key, and the returned fields, followed by two short caveats. No padding, no repeated title, nothing that could be cut without losing 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?

For a one-parameter read tool with full annotations and no output schema, the description compensates by naming the returned data classes and by flagging the interpretive caveat. What remains uncovered is failure behavior for an invalid publicId and any explicit routing to the batch sibling, which keeps it short of a 5.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains both the pattern and where to obtain the publicId (search result or the last segment of a canonical URL). The description only restates that the lookup is by publicId, adding no new meaning. Baseline 3 applies when the schema does the heavy lifting.

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?

"Liest eine Anzeige anhand ihrer publicId" gives a specific verb plus resource and the identifying key, then enumerates the content returned (Arbeitgebertext, Vergütung, Berufserlaubnis-Belege, Quellen). The singular "eine Anzeige" implicitly separates it from the plural sibling lese_stellenanzeigen, but that sibling is never named, so the differentiation is left to inference.

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 description makes clear this is a single-record read, and the closing sentence draws a negative boundary ("führt keine Bewerbung aus"), which tells the agent this is not an action tool. However it never says when to prefer it over lese_stellenanzeigen (batch), fetch, or search, nor does it state prerequisites such as obtaining the publicId first — that hint lives only in the schema.

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