Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

german_jobs_scraper

Read-onlyIdempotent

German Jobs Scraper - Arbeitsagentur Vacancies: Real-time structured data extraction feed for German Jobs Scraper - Arbeitsagentur Vacancies.

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": "german_jobs_scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered structurally. The description contributes only the word 'real-time', and says nothing about result freshness, rate limits, pagination, or what a record contains. It does not contradict the annotations, but it adds almost nothing to them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short, but only because it repeats the name and title in a self-referential loop rather than front-loading useful information. Length is not the problem; the sentence carries no substance.

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

Completeness2/5

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

The tool is simple and the annotations and parameter schema cover the mechanical details, but the description leaves an agent unable to distinguish this scraper's data, coverage, or output shape from any other job-listing tool. Given no output schema exists, more context about returned records was warranted.

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?

With a single optional parameter and 100% schema description coverage, the schema fully documents maxResults. The description adds no meaning about defaults, limits, or result ordering, so the baseline of 3 applies.

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

Purpose2/5

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

The text merely restates the tool name and title ('Real-time structured data extraction feed for German Jobs Scraper - Arbeitsagentur Vacancies'), a circular sentence that adds no verb or scope beyond the name itself. An agent can infer it scrapes Arbeitsagentur job vacancies only because the name already says so, not because the description explains it.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of any alternative such as the sibling job-board scrapers. Nothing tells an agent why it would pick this over the other listings tools.

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