Skip to main content
Glama

Draft a job application (Bewerbung) by email

draft_job_application
Read-onlyIdempotent

Use this when the user wants to apply for one of their matched jobs (Bewerbung). Drafts an application by email: recipient, subject, cover letter and the stored resume document as attachment. Sends nothing. Show the user the draft, let them edit the cover letter and sign it with their name. If the posting asks for more (salary expectation, earliest start date, a cover letter, certificates), forderungen names each with a hint; the cover letter then holds a line with [bitte eintragen] to fill in or remove before sending. Without an email address in the posting, the call is refused. Scope: cv:lesen.

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": {
      "stelleId": "<stelleId>"
    },
    "name": "draft_job_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
stelleIdYes

Output Schema

NameRequiredDescriptionDefault
urlYes
titelYes
anhangYes
betreffYes
stelleIdYes
empfaengerYes
anschreibenYes
arbeitgeberYes
forderungenYes
empfaengerHerkunftYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / empfaengerHerkunft
      Added value: +{
      +  "enum": [
      +    "anzeige",
      +    "pruefkonto"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "stelleId",
      -  "titel",
      -  "arbeitgeber",
      -  "url",
      -  "empfaenger",
      -  "betreff",
      -  "anschreiben",
      -  "anhang",
      -  "forderungen"
      -]New value: +[
      +  "stelleId",
      +  "titel",
      +  "arbeitgeber",
      +  "url",
      +  "empfaenger",
      +  "empfaengerHerkunft",
      +  "betreff",
      +  "anschreiben",
      +  "anhang",
      +  "forderungen"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing that nothing is sent, that the call is refused when the posting lacks an email address, that extra requirements surface in 'forderungen', and that placeholders marked [bitte eintragen] are inserted into the cover letter. It also names the required scope cv:lesen, which an agent needs before calling.

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?

Front-loaded with the trigger and the produced artifact, then progresses to safety, post-call workflow, edge cases, and scope. Dense but every sentence carries operational information; there is no filler.

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

Completeness5/5

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

For a one-parameter tool with an output schema and full annotations, the description covers the trigger, what gets produced, what is not done, refusal conditions, and the user-facing follow-up. Nothing an agent needs to invoke it correctly is missing.

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?

The single parameter stelleId has zero schema description coverage, so the description carries the burden; it implies the id identifies a matched job posting (used to look up the recipient address and requirements) but never states the id format or source list explicitly. Partial compensation only, so baseline-plus rather than a strong 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and artifact: 'Drafts an application by email: recipient, subject, cover letter and the stored resume document as attachment.' The clause 'Sends nothing' plus the sibling name send_job_application makes the boundary between drafting and sending unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opening line gives a clear trigger ('when the user wants to apply for one of their matched jobs') and the description prescribes a follow-up workflow (show the draft, let the user edit and sign). It does not name the send_job_application sibling as the explicit alternative for actually sending, so routing is implied rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources