swarm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FOURSQUARE_TOKEN | Yes | Your Foursquare OAuth2 access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_checkinsB | Get the authenticated user's check-in history. Returns check-ins with venue info, timestamps, and optional photos. |
| get_checkins_by_date_rangeA | Get check-ins within a specific date range. |
| get_recent_checkinsC | Get check-ins from the past X days. |
| get_checkin_detailsB | Get detailed information about a specific check-in by ID. |
| get_all_checkinsA | Get ALL check-ins by paginating through the entire history. EXPENSIVE: Makes 1 API call per 250 check-ins (e.g., 5000 check-ins = 20 API calls). Prefer get_checkins with manual pagination for incremental access. |
| get_checkin_statsA | Get statistics about your check-in history (total count, date range, etc.) |
| get_categoriesA | Get all unique venue categories from your check-in history with counts. Useful for discovering what categories exist before filtering. EXPENSIVE: Scans entire history. |
| search_checkinsA | Search check-ins with flexible filters. EXPENSIVE: Requires client-side filtering. Use filters to narrow results. For comprehensive searches, increase max_scan. |
| get_venue_detailsA | Get detailed information about a venue by ID, including ratings, hours, tips, and photos. Venue IDs are included in check-in data. |
| get_top_venuesA | Get your most visited venues with visit counts. EXPENSIVE: Scans check-in history to aggregate venue visits. |
| get_server_infoA | Get information about this MCP server: data sources, privacy scope, available tools, and their costs. Cheap introspection call with no external API requests. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: get_all_checkins vs get_checkins differ in pagination cost, get_checkins_by_date_range vs get_recent_checkins target different time ranges, and others cover categories, stats, venues, and server info. Descriptions explicitly clarify overlaps.
All tool names follow a consistent get_verb_noun pattern in snake_case (e.g., get_all_checkins, get_categories, get_checkin_stats). No mixing of naming conventions, making it easy to infer function.
With 11 tools, the server covers all major retrieval needs for check-in history and venue data without being bloated. The count is well-scoped for a focused analytics domain.
The server provides comprehensive read access: full history, filtered, stats, categories, top venues, and venue details. Missing write/update tools aligns with use case. A minor gap is no direct tool to list check-ins for a specific venue, but search_checkins can approximate this.