myFlohmarkt Flea Market Catalog

Search flea markets in Germany

search_events

Read-onlyIdempotent

Search German flea markets (Flohmarkt, Trödelmarkt, Hofflohmarkt, Kinderflohmarkt, Antik- und Sammlermarkt) from the public my-flohmarkt.de catalogue. Filter by free text, by city name or postal code (PLZ) via the city argument, by date range, or by radius around a coordinate. Radius searches require lat, lng, and radiusKm together (max 100 km). Each hit carries title, date, start and end time, PLZ, city, coordinates, market type and the public event URL. Returns at most 50 results plus a dataAsOf timestamp.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	No
`lng`	No
`city`	No
`limit`	No
`query`	No
`dateTo`	No
`dateFrom`	No
`radiusKm`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`total`	Yes
`dataAsOf`	No
`totalIsLowerBound`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedOct 13, 2026
- removedOutput schema / properties / dataAsOf / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / dataAsOf / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / city / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / city / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / date / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / date / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / imageUrl / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / imageUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / lat / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / lat / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / lng / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / lng / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / marketType / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / marketType / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / participants / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / participants / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / plz / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / plz / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / timeFrom / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / timeFrom / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / timeTo / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / timeTo / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / updatedAt / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / updatedAt / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedSep 5, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: the 50-result cap, the dataAsOf freshness timestamp, the 100 km radius ceiling, and the source of truth for the data. It does not discuss error behavior or empty-result handling, keeping it just under a 5.

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?

Three dense sentences with zero filler: purpose and source first, then the filtering modes and the radius constraint, then the return-shape summary. Every sentence adds information an agent needs to call the tool correctly.

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?

An output schema exists, yet the description still usefully previews the hit fields (title, date, times, PLZ, city, coordinates, market type, URL), the result cap and the dataAsOf timestamp. Combined with the filter and radius constraints, nothing needed to invoke this read-only search correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry all parameter meaning, and it largely does: query = free text, city = city name or PLZ, dateFrom/dateTo = date range, and the coupled lat/lng/radiusKm triple with its 100 km maximum. Only limit's default of 10 is not restated, but the 50-result hard cap is disclosed instead.

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?

Names a specific verb and resource ('Search German flea markets') and pins the source catalogue (my-flohmarkt.de), including the German market-type vocabulary it covers. An agent can distinguish this list/search tool from get_event (single market) and recently_updated_events without opening a schema.

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 concrete usage context: filter by free text, city/PLZ, date range, or radius, and states the hard requirement that radius searches need lat, lng and radiusKm together (max 100 km). It stops short of naming when to prefer a sibling such as get_event, so it is clear context without explicit alternatives or exclusions.

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

All myFlohmarkt Flea Market Catalog tools Inspect

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

Need Help?