Skip to main content
Glama

jobsuche_update_offer_status

Update an offer's application status and notes to track progress from new to applied, shortlisted, rejected, or ignored. Use the offer reference number to keep history accurate.

Instructions

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

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>",
      "status": "<status>"
    },
    "name": "jobsuche_update_offer_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional notes for history tracking.
refnrYesOffer Referenznummer to update.
statusYesNew application lifecycle status.
db_pathNoOptional override path for SQLite database.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and leaves key mutation behavior undisclosed: whether the status transition is validated, whether 'notes' appends to history or overwrites it, whether the call is idempotent, and what happens if refnr is unknown. It does not even state that this writes to a persistent store (the db_path parameter hints at SQLite but that is schema, not description).

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?

A single front-loaded sentence with no filler; the verb, resource, and allowed values all come first. Nothing could be removed without losing information.

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 a four-parameter mutation tool with no annotations and no output schema, the definition covers what changes but not the safety or result profile — no confirmation of what is returned, whether a record is created if absent, or how failures surface. Schema documentation is complete, which keeps it at minimum viable rather than inadequate.

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 including the status enum and the notes/db_path purpose is already documented in the schema; the description merely repeats the status values. Baseline 3 applies since the schema does the heavy lifting and the description adds no extra semantic detail such as whether notes are cumulative.

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 uses a specific verb ('Update') plus the exact resource ('an offer's application status') and enumerates the valid lifecycle states, so an agent immediately knows the operation. It does not explicitly differentiate from siblings, but none of the listed siblings (fetch_offer_details, list_offers, search_ausbildung, sync_and_export, auth_status) overlaps in function, so confusion risk is low.

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 statement of when to use this tool, when not to, or what precedes it — e.g. whether the offer must first be tracked/locally stored, or whether this is the only way to advance a lifecycle state. The caller must infer the usage context entirely from the tool name and status enum.

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