This server has basic tool definitions with descriptions and input schemas present for all 5 tools. However, there are significant quality gaps: (1) Tool names do not follow verb_noun conventions consistently, 'buscar_calle', 'buscar_numero', 'buscar_inmuebles' are Spanish verb forms, not English action verbs expected in MCP tool naming. (2) Descriptions are present but often lack depth, they state WHAT the tool does but rarely explain WHEN to use it or what distinguishes it from similar tools. For example, 'buscar_inmuebles' and 'buscar_numero' have overlapping purposes but no guidance on which to call. (3) Parameter descriptions are minimal and sometimes redundant with names (e.g., 'Código de la calle' for a 'calle' param). (4) No documented output schemas, the code parses XML responses but does not show LLMs what fields they should expect. (5) Error handling is present in code (parse_xml_error function) but not surfaced in tool descriptions. (6) No parameters have enums, ranges, or format constraints documented in descriptions. The server is functional but falls short of production-grade clarity and LLM-optimization standards.

• Rename all tools to English following verb_noun convention: buscar_calle → search_street, buscar_numero → search_property_number, buscar_inmuebles → search_properties, obtener_inmueble → get_property, buscar_por_coordenadas → search_by_coordinates. MCP standard is English; LLMs rely on English names for intent inference.
• Document output schemas in tool descriptions. E.g., 'Returns a list of matching properties with fields: referencia_catastral, direccion, provincia, municipio, superficie_m2, tipo. Large result sets are paginated (see limit parameter).'
• Add pagination parameters (limit: 1 - 100, default 20; offset or page: 0 - based) to list-returning tools. Document: 'Results are limited to 20 per call. Use offset to fetch additional pages.'
• Clarify tool purposes in descriptions. E.g., for search_property_number: 'Call this after search_street to find specific building numbers on a known street. Returns the nearest number if exact match not found.' For search_properties: 'Direct search for properties by full address (provincia, municipio, calle, numero). Use when you have complete address. Otherwise, use search_street → search_property_number workflow.'
• Add constraint documentation to parameters. E.g., referencia_catastral: 'Cadastral reference: 14 - 20 digit string (format: 2-digit province + 3-digit municipality + 1-digit sector + 2-digit parcel + 2-digit subparcel + 2 - 4 digit control characters).' Include format regex in schema if possible.
• Document error scenarios in tool descriptions: 'Returns error if provincia or municipio code is invalid. Catastro codes are listed at [URL]. If error, try search_street with just street name to discover correct codes.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry