laspalmas-avisos-mcp
Related Servers
Alternatives to laspalmas-avisos-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI agents to report street incidents to Valencia City Council by listing categories, geocoding streets, checking existing reports, and creating nuevos avisos from text or photos with human-confirmed previews. Supports stdio and HTTP transports, with identity and device registration handled locally.11AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with IoT device data from a smart city, including public lighting, water, and gas meters. Supports querying and management via the Model Context Protocol.1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to look up official cadastral parcels across 31 European country and region codes by reference, coordinates, or free-text Spanish address, returning location, area, land use, and outlines while also estimating solar and agricultural potential, market prices, and investment scores.9256 npmMIT
- AlicenseAqualityDmaintenanceProvides access to real-time Winnipeg Transit data and 311 City Services, enabling AI assistants to plan trips, check bus arrivals, and search for reported city issues. It allows users to interact with city infrastructure data and transit schedules through natural language.81MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query Brazilian municipal transparency portals for payroll, expenses, contracts, bids, revenues, and legislation using natural language in Portuguese.MIT
- AlicenseAqualityBmaintenanceLets an AI agent query Yerevan's live municipal GIS data—air quality, cadastral parcels, zoning, construction, and transport—with no API key.247MIT
TDQS
Scored across 8 tools
Tools generally target distinct resources and actions: identity get/set, service/category listing, category suggestion, aviso listing, and aviso creation. The main overlap is between create_aviso and create_aviso_from_photo, but the photo-specific workflow is clearly differentiated by description.
Most tool names follow a predictable snake_case pattern with verb_noun structure (get_identity, set_identity, list_services, create_aviso). The outlier my_avisos uses a possessive/noun phrase rather than a verb, but overall conventions remain readable and mostly consistent.
With 8 tools, the set is well-scoped for a municipal incident-reporting assistant. Each tool earns its place by covering identity, lookup, suggestion, listing, and creation workflows without excessive surface area.
Core lifecycle coverage exists: identity setup, service/category discovery, category suggestion, listing one's avisos, and creating avisos with or without a photo. Minor gaps include no explicit get_aviso detail or status tool and no update/cancel operation, though these may be outside the intended API scope.