Skip to main content
Glama

jobsuche_fetch_offer_details

Fetch full job offer details, requirements, and employer contact information by Jobsuche reference number, with optional API, browser, or hybrid enrichment and SQLite updates.

Instructions

Fetch full description, requirements, and employer contact details for a Jobsuche refnr.

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": {
      "refnr": "<refnr>"
    },
    "name": "jobsuche_fetch_offer_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoEnrichment mode: api (default), browser, or hybrid.
refnrYesUnique Jobsuche Referenznummer (e.g. 10000-1206415041-S).
persistNoWhether to update the offer in SQLite if present (default: true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and fails to disclose side effects: the 'persist' flag implies a SQLite write and 'mode' selects api/browser/hybrid strategies, but none of that behavior, its reversibility, or its cost is described. It also says nothing about return format or latency, which matters especially for the browser mode.

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?

One sentence, front-loaded with the verb and the payload contents, with no redundant restatement of the name. It is efficient, though its brevity is partly the cause of the missing behavioral detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations, no output schema, and an implicit database-mutating parameter (persist defaults to true), the description is too thin. An agent cannot tell what it gets back, what the enrichment modes cost, or that a write may occur as a side effect.

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%, so refnr, mode, and persist are already documented in the schema; baseline 3 applies. The description only reinforces that refnr identifies a Jobsuche offer and adds no meaning about what the modes actually do or when to choose browser vs hybrid.

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 names a specific verb ("Fetch") and resource (offer details) and enumerates the payload: full description, requirements, and employer contact details, keyed by refnr. It is distinguishable from list/search siblings by the word "full" and the singular refnr key, but it never explicitly contrasts itself with them.

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: nothing says this should follow a listing/search result, no prerequisites or auth requirements, and no exclusions. The agent must infer from the sibling names that details are fetched after an offer is located.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.