Venue demand data (saunas, bowling, trampoline, golf sims, pickleball): query rows, no key needed.
Scored across 4 tools
The four tools have broadly different roles, but search and data both return sample-day rows, while fetch and search both return document-like content. The dense descriptions add operational guidance rather than sharply separating tool boundaries, so an agent may hesitate between search, data, and fetch for a given lookup.
All names are lowercase and short, which is readable, but the set mixes nouns (about, data) with verbs (fetch, search). There is no consistent verb_noun pattern or single grammatical convention.
Four tools is a well-scoped surface for a read-only research data API: metadata, structured queries, document retrieval, and natural-language search each have a clear place. The count is neither bloated nor trivially thin.
The surface covers discovery (about/search), structured data access with endpoint chaining, and document retrieval. Minor gaps remain around explicit key/auth handling and possibly listing documents directly, but core read-only research workflows are covered.
What Fron Research and its Check sites measure (saunas, bowling, trampoline parks, golf simulators, pickleball), their URLs, plans, free sample days and every document id.
Inputs: no named parameters.
Structured rows from the Fron Research Data API (https://api.fronresearch.com/v1): markets, venues, bookable slots and a utilization and a revenue estimate per venue, market or day. Without a key every query reads one free sample day for every venue, whatever dates are asked (the response's tier, free_day and range say what was read); a caller that connects to https://fronresearch.com/api/agent with "Authorization: Bearer " reads the history its plan covers (a site's own /api/agent does not forward keys). Start with endpoint index (the sample day and endpoints), then markets or venues to get ids, then metrics. Fields, filters and how to get a key: https://fronresearch.com/data/history/
Inputs: endpoint (required), params, venue_id.
Read one document by id (from search or about). sample/ returns that site's free example day as rows, CC BY 4.0.
Inputs: id (required), offset.
Ask a question in plain language. Returns the most relevant passages from the public pages of Fron Research and its sites, each with its canonical URL to cite, plus the matching free sample days. answer.instruction says how to use them; followUp.questions are optional questions for your user, whose answers go in intent next time.
Inputs: query (required), site, intent, maxResults.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Indoor golf simulator demand data: query venues, markets and rollups, plus public pages. No key.
Bowling center demand data: query venues, markets and rollups, plus public pages. No key.
Pickleball and padel club demand data: query venues, markets and rollups, plus public pages. No key.
Trampoline park demand data: query venues, markets and rollups, plus public pages. No key.
Add one secure layer between your agents and this server.