Skip to main content
Glama

jobsuche_sync_and_export

Synchronize Ausbildung offers from the Jobsuche API into SQLite, score and group them by company, then export LLM-ready Markdown/JSON packages to the exports directory.

Instructions

Synchronize Ausbildung offers from Jobsuche API into SQLite, score and group by company, and export LLM-ready Markdown/JSON packages to exports/.

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

Input Schema

NameRequiredDescriptionDefault
woNoCity or postal code (default: Aachen).
plzNoOptional 5-digit postal code.
wasNoProfession search term.
limitNoOptional maximum offers to sync.
db_pathNoOptional override path for SQLite database.
umkreisNoRadius in km (>= 0, default: 25).
export_dirNoOptional override path for exports directory.
enrich_detailsNoFetch pc/v4/jobdetails for each offer before exporting (default: true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose real side effects: writes into a SQLite database, creates files under exports/, and optionally issues per-offer network calls to pc/v4/jobdetails. It omits auth requirements, rate limiting, whether existing DB rows or export files are overwritten, and whether repeated runs are idempotent.

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?

A single front-loaded sentence with the action verb first and the pipeline stages in execution order; every clause carries information. It is dense but not padded.

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 an 8-parameter mutation-and-export tool with no annotations and no output schema, the description covers the pipeline shape and default export location but says nothing about what is returned, error behavior, or the auth precondition. An agent could invoke it but cannot predict its results or failure modes from the description alone.

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 all 8 optional parameters are already documented, and the description adds little param-level meaning beyond tying exports to the exports/ directory. The scoring/grouping logic is not exposed as a parameter, so there is no extra semantics to convey.

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 concrete multi-stage operation: sync Ausbildung offers from the Jobsuche API into SQLite, score/group by company, and export Markdown/JSON to exports/. That verb-and-resource specificity separates it from the read-oriented siblings (search_ausbildung, list_offers, fetch_offer_details), even though no sibling is named explicitly.

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 explicit when-to-use or when-not guidance and no stated prerequisites (e.g., needing a valid session via jobsuche_auth_status) or cost/runtime warnings. The batch-pipeline framing implies usage, but an agent must infer that quick lookups should go to the search/list siblings instead of this heavy sync tool.

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