Skip to main content
Glama

myFlohmarkt Flea Market Catalog

by de.my-flohmarkt

Get flea market details

get_event
Read-onlyIdempotent

Get the full public details of one German flea market by its UUID, as returned in the id field of search_events or recently_updated_events: description text, street address, date and opening times, market type and topics, entrance fee and seller stand fee, stand sizes and table rental, whether sellers can still sign up, and the public my-flohmarkt.de event URL. Use it when a search hit is not enough to answer about price, address or what is sold. Unknown or non-public UUIDs return not_found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
eventNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds a concrete behavioral trait beyond them: unknown or non-public UUIDs return not_found. It also clarifies the scope to public details of German flea markets, which is useful context for an agent selecting the tool.

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?

The description is long but every sentence earns its place. It front-loads the core purpose, then lists the valuable fields, gives a direct usage trigger, and ends with the error behavior. No redundant or tautological wording.

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?

With an output schema present, return-value details are already covered structurally. The description covers input provenance, selection criteria, scope limitation to public German markets, and error semantics. Nothing important is missing for correct invocation.

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?

The single id parameter has no schema description (0% coverage), but the description fully compensates by explaining the ID comes from the id field of search_events or recently_updated_events and what happens for unknown/non-public UUIDs. This is meaning beyond the schema's UUID format and pattern.

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?

The description states a specific action and resource: getting the full public details of one German flea market by UUID, and enumerates the exact fields returned. It also differentiates itself from sibling tools by referencing the id field of search_events or recently_updated_events, making its scope immediately clear.

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

Usage Guidelines5/5

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

Explicitly says when to use the tool: when a search hit is not enough to answer questions about price, address, or what is sold. It names the sibling tools that supply the ID and implies alternatives by distinguishing full details from search hits.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

The three tools have clearly distinct purposes: one searches by criteria, one lists recent additions, and one fetches full details for a specific UUID. There is no meaningful overlap or ambiguity in when an agent should choose each.

Naming Consistency4/5

Two tools follow a clear verb_noun pattern (search_events, get_event), while recently_updated_events uses an adjectival prefix instead of an imperative verb. The naming is still predictable and readable, with consistent snake_case and the shared 'event/events' noun.

Tool Count5/5

Three tools is well-scoped for a read-only public catalogue: discover recent entries, search by filters, and retrieve full details. Each tool adds a distinct capability without unnecessary bloat.

Completeness5/5

For a read-only flea market catalogue, the surface covers the full user journey: finding events via search or recent updates, then getting complete details. No CRUD operations are expected, so there are no obvious gaps.

Resources