laspalmas-avisos-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_identityA | Devuelve la identidad guardada (email, teléfono, uuid) o null si aún no se preguntó. |
| set_identityB | Guarda email y teléfono del comunicante (se preguntan UNA vez y se reutilizan; el uuid se genera solo). |
| list_servicesC | Servicios de LPGC Avisa (id + título). |
| list_categoriesC | Categorías de un servicio (id + título). |
| suggest_categoriesB | Sugiere service_id + category_id por palabras (p.ej. 'contenedor desbordado'). |
| my_avisosC | Avisos del email guardado (o el indicado). |
| create_avisoA | Crea un aviso. IMPORTANTE: por defecto es DRY-RUN (confirm=false) y solo devuelve el payload que se enviaría, SIN crear nada. Para crear de verdad hay que pasar confirm=true. Usa la identidad guardada salvo 'identity'. |
| create_aviso_from_photoA | Aviso desde una FOTO en fases. VÍA PREFERIDA: sube la foto con PUT /upload (curl) y pasa file_id; por stdio usa image_path local. Sin service_id/category_id → sugiere (need_category). Con todo → preview + preview_token SIN enviar. Envío: MISMOS campos + confirm:true + human_confirmed:true + preview_token (tras 'sí' humano). Sin las tres NO se envía. La foto viaja en el envío (base64). |
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 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.