Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

query_european_and_regional_markets

Read-onlyIdempotent

Query European labor vacancies, Southeast European marketplace listings, or Turkish central bank FX, bullion, fuel, real estate, and mobility datasets by keyword and record limit.

Instructions

Query European labor market vacancies (German Arbeitsagentur), Southeast European marketplace listings (Croatia, Slovenia, Bosnia, Serbia, North Macedonia, Albania), or Turkish central bank FX, bullion, fuel, real estate, and mobility datasets.

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": {
      "dataset": "<dataset>"
    },
    "name": "query_european_and_regional_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional search keyword, city name, or currency/asset filter.
datasetYesTarget regional marketplace, labor, or macroeconomic dataset to query.german_jobs_arbeitsagentur
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered without description help. The description adds nothing about data freshness, upstream rate limits, per-dataset result caps, or whether some datasets are scraped/volatile — meaningful context for a 21-source aggregator.

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

Conciseness4/5

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

A single front-loaded sentence that leads with the geographic scope and then enumerates source families; there is no filler or restatement of the tool name. It is slightly list-heavy and drops several dataset families, which weakens it marginally but does not bloat it.

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?

The parameters are fully documented in-schema and annotations carry the safety profile, so the basics are covered. However, for a tool that multiplexes 21 heterogeneous datasets with no output schema, the description should indicate that return shapes differ by dataset and that results are capped by maxResults, neither of which it does.

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%, with the dataset enum, query string, and maxResults bounds all documented in-schema, so the baseline of 3 applies. The description adds only a loose gloss on what query filters against (keyword, city, currency/asset) and says nothing about how query semantics differ across datasets, such as whether it matches listing titles vs currency codes.

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?

Names a specific verb (Query) and concrete resources: German Arbeitsagentur vacancies, Balkan classifieds by country, and TCMB FX/bullion/fuel/real-estate/mobility data. This clearly separates it from siblings like search_eu_ted_public_tenders or monitor_global_seismic_events, though the enumeration covers only part of the 21 enum datasets (crypto tickers, weather, pharmacies, prayer times, hotels, ferries, flights are unmentioned).

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

Usage Guidelines3/5

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

Usage is only implied: the description tells you what data exists so you can pick it, but gives no explicit when-to-use vs when-not guidance, no prerequisites, and no advice on choosing between overlapping datasets (e.g. the two Serbia classifieds sources). Sibling overlap is minimal, which limits the harm.

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