Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
jobsuche_search_ausbildungC

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

jobsuche_fetch_offer_detailsC

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

jobsuche_sync_and_exportB

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

jobsuche_list_offersB

List and filter tracked Ausbildung offers stored in SQLite.

jobsuche_update_offer_statusB

Update an offer's application status (new, shortlisted, drafted, applied, rejected, ignored) and notes.

jobsuche_auth_statusA

Check Bundesagentur für Arbeit session state, credentials, and 6-digit TOTP generator readiness.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 6 tools

Disambiguation4/5

Each tool has a distinct role: remote search (search_ausbildung), remote detail fetch (fetch_offer_details), local tracking queries (list_offers), and status mutation (update_offer_status). The main potential confusion is list_offers vs. search_ausbildung, but descriptions clearly signal local SQLite vs. live API, so misselection risk is low.

Naming Consistency4/5

All tools share the jobsuche_ prefix and mostly follow verb_noun style (fetch_offer_details, list_offers, search_ausbildung, update_offer_status, sync_and_export). auth_status deviates as a noun phrase, and sync_and_export bundles two actions, but the pattern remains readable and predictable.

Tool Count4/5

Six tools cover a focused workflow (auth, search, fetch, sync/export, list, update) without redundancy. It is slightly lean — no removal/pruning operation and no standalone scoring tool — but each tool earns its place for this niche pipeline.

Completeness4/5

The core lifecycle is covered: session auth, discovery via search, detail retrieval, local tracking, status mutation, and bulk export. Minor gaps exist (no delete/archive of tracked offers, no manual add, no separate rescore), but agents can work around them via update_offer_status (e.g., 'ignored').

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues