Skip to main content
Glama
Sign In

Jobroulette

by de.jobroulette
OverviewDiscussionsAdmin

Withdraw consent to an introduction to an employer

withdraw_employer_introduction
DestructiveIdempotent

Use this when the user wants to take back their consent to be introduced to an employer for a job (Zustimmung zur Vermittlung widerrufen). Works until Jobroulette has presented the user; after that the employer handles the data on its own responsibility, and this tool fails and says so. A second call changes nothing. Scope: vermittlung:zustimmen.

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the offer from list_employer_introductions.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
standYes
titelYes
gefragtAmYes
standorteYes
arbeitgeberYes
stelleGeloeschtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedOutput schema / properties / antwort
      Removed value: -{
-  "anyOf": [
-    {
-      "enum": [
-        "ja",
-        "nein"
-      ],
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • removedOutput schema / properties / beantwortetAm
      Removed value: -{
-  "anyOf": [
-    {
-      "format": "date-time",
-      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • removedOutput schema / properties / cvFassungVom
      Removed value: -{
-  "anyOf": [
-    {
-      "format": "date-time",
-      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • removedOutput schema / properties / cvVorhanden
      Removed value: -{
-  "type": "boolean"
-}
    • removedOutput schema / properties / kanal
      Removed value: -{
-  "anyOf": [
-    {
-      "enum": [
-        "mail",
-        "deck",
-        "mcp"
-      ],
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • addedOutput schema / properties / stand
      Added value: +{
+  "enum": [
+    "offen",
+    "abgelehnt",
+    "zugestimmt",
+    "widerrufen",
+    "vorgestellt"
+  ],
+  "type": "string"
+}
    • removedOutput schema / properties / vorgestelltAm
      Removed value: -{
-  "anyOf": [
-    {
-      "format": "date-time",
-      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • removedOutput schema / properties / widerrufKanal
      Removed value: -{
-  "anyOf": [
-    {
-      "enum": [
-        "mail",
-        "deck",
-        "mcp"
-      ],
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • removedOutput schema / properties / widerrufenAm
      Removed value: -{
-  "anyOf": [
-    {
-      "format": "date-time",
-      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • changedOutput schema / required
      Previous value: -[
-  "id",
-  "arbeitgeber",
-  "titel",
-  "standorte",
-  "url",
-  "stelleGeloescht",
-  "gefragtAm",
-  "antwort",
-  "beantwortetAm",
-  "kanal",
-  "cvFassungVom",
-  "cvVorhanden",
-  "widerrufenAm",
-  "widerrufKanal",
-  "vorgestelltAm"
-]New value: +[
+  "id",
+  "arbeitgeber",
+  "titel",
+  "standorte",
+  "url",
+  "stelleGeloescht",
+  "gefragtAm",
+  "stand"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the temporal cutoff (works until the user has been presented), what happens after (employer handles data on its own responsibility), the failure behavior ('fails and says so'), and the required scope vermittlung:zustimmen. The 'second call changes nothing' note reinforces idempotentHint with concrete meaning.

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 triggering user intent, then the precondition, the failure mode, and the scope — each sentence carries distinct information with 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?

Covers trigger, precondition, failure behavior, idempotency, and authorization scope; an output schema exists so return values need not be explained. An agent has everything needed to call this correctly and interpret a failure.

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 coverage is 100% and the single `id` parameter is fully documented in the schema, including the pointer to list_employer_introductions. The description adds no further parameter detail, so the baseline of 3 applies.

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?

States a specific verb and resource ('take back their consent to be introduced to an employer'), reinforced by the German term (Zustimmung zur Vermittlung widerrufen), so the action is unambiguous. It does not explicitly differentiate itself from the sibling decline_employer_introduction, which is the most likely confusion point.

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?

Gives a clear triggering condition ('Use this when the user wants to take back their consent') and a boundary condition: it only works until Jobroulette has presented the user, after which it fails. No alternative tool is named for the post-presentation case, which keeps it short of a 5.

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

All Jobroulette toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources