get_place — Agenda Rio MCP Tool Read-only
get_place
(get place) is one of 26 tools on the
Agenda Rio
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_place from your client
- Claude Code Agenda Rio get_place run in your project directory
- Claude Desktop Agenda Rio get_place ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agenda Rio get_place ~/.cursor/mcp.json
- VS Code Agenda Rio get_place .vscode/mcp.json
- Zed Agenda Rio get_place ~/.config/zed/settings.json
- Windsurf Agenda Rio get_place ~/.codeium/windsurf/mcp_config.json
- Cline Agenda Rio get_place ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agenda Rio get_place ~/.gemini/settings.json
- Grok Agenda Rio get_place .mcp.json (in your project root)
- ChatGPT Agenda Rio get_place Settings → Connectors → Advanced → Developer mode
- Claude.ai Agenda Rio get_place Settings → Connectors → Add custom connector
- LangChain Agenda Rio get_place pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agenda-rio-br https://agenda.rio.br/mcpOther tools on this server
- get_site_info
- list_categories
- search_places
- list_events
- list_guides
- list_booking_services
- get_availability
- create_booking
- reserve_event_tickets
- request_reservation
- rsvp_event
- get_event_tickets
- list_products
- create_checkout
- get_restaurant_menus
- search_dishes
- list_pricing_plans
- get_reviews
- list_blog_posts
- list_faqs
- list_forms
- submit_form
- get_loyalty_info
- list_offers
- list_profiles
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.