Skip to main content
Glama

jobsuche_search_ausbildung

Search Bundesagentur für Arbeit for Ausbildung offers by profession, city, postal code, or radius, with optional start-date filters. Return or persist matching listings for review.

Instructions

Search Bundesagentur für Arbeit (arbeitsagentur.de) for Ausbildung offers (default: Fachinformatiker/in für Systemintegration in Aachen, 25 km radius).

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_search_ausbildung"
  }
}

Input Schema

NameRequiredDescriptionDefault
woNoCity or 5-digit PLZ (default: Aachen).
plzNoOptional 5-digit German postal code.
wasNoProfession or search query (default: Fachinformatiker/in für Systemintegration).
modeNoDiscovery mode: api (default), browser, or hybrid.
limitNoMaximum number of offers to return.
abdatumNoOptional start date filter (YYYY-MM-DD).
persistNoWhether to persist discovered offers into SQLite (default: true).
umkreisNoSearch radius in km (>= 0, default: 25).

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 exist, so the description carries the full behavioral burden and it discloses almost nothing beyond the search subject. It never mentions that results are persisted to SQLite by default, that a browser/hybrid mode may be used (with different latency or reliability characteristics), or whether any authentication or rate limits apply to the arbeitsagentur.de backend.

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 source system first and the defaults tucked into a parenthetical. It is tight, though the defaults repeat schema content and do not earn their space in a description this short.

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?

With 8 optional parameters, three discovery modes, and a persistence side effect, the tool is non-trivial, yet there is no output schema and the description says nothing about what is returned or in what form. An agent can construct a call from the schema but cannot predict the response shape or the SQLite 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 every parameter is already documented, and the description's stated defaults (city, profession, radius) merely restate what the schema says. It adds no semantics about how wo and plz interact, how mode changes request behavior, or what limit defaults to.

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 (search) and a concrete resource (Ausbildung offers on arbeitsagentur.de), with the source domain and default query spelled out. It is clear what the tool does, but it offers no differentiation from siblings such as jobsuche_list_offers or jobsuche_fetch_offer_details, so an agent cannot tell from the text alone which one to reach for.

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, when-not-to-use, or alternative-tool guidance. The only usage signal is the parenthetical defaults (Fachinformatiker/in, Aachen, 25 km), which hints at a typical query but does not tell the agent when to prefer this over list_offers or fetch_offer_details.

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