GILLBY FIELD NOTES / 03
Standalone learning tool · built with the Gillby API
What do we actually know?
Can one beach sample describe every day? Place the latest available beach sample on a calendar and explore the days it cannot describe.
Free to explore. No account needed. A public demonstration separate from Gillby’s signed-in planning app.
Make a discovery.
The API supplies a recent sample near the selected place. Check the actual returned site; it may differ from the place name.
Drawing the coastline…
Location coordinates & source
Boca Inlet · 26.33940, -80.07220
Source: Gillby public spot directory, fixed reference points (WGS84).
Choose your inputs, then run a public API request. No sample values are preloaded.
What did you notice?
- How old is the returned sample? How is that different from the API response time?
- What changes when you extend the calendar? Does the amount of known evidence change?
- What extra records would you need to investigate a trend?
How this was built
This standalone demonstration calls Gillby’s public HTTP API directly from your browser, then compares the returned values here. It uses the same public endpoints available to other builders. It does not call MCP behind the scenes.
See API requests, source metadata & raw responses
Run the experiment to see the exact requests, time window and unmodified responses.
Repeat it with MCP
Connect a compatible assistant to https://www.gillby.com/mcp, then use this prompt. The assistant should verify tool inputs and retain source limitations.
Use Gillby get_beach_bacteria with spot=boca-inlet. Report the returned site, sampledAt, status, source metadata and response time. Explain that this is a recent sample record, not a complete sampling history or a current all-clear. Do not infer untested days.
API quickstart · OpenAPI schema · MCP setup · Citation guidance