Skip to main content
Glama

Buscar profesionales

buscar_profesionales
Read-onlyIdempotent

Busca profesionales de oficios en una ciudad o distrito de Latinoamérica (Perú, Colombia, México, Chile y más) en el directorio público de HALPII. Recibe la necesidad en palabras de la persona («se rompió el caño de la cocina») o el oficio («gasfitero»), deduce el oficio y devuelve hasta 6 profesionales con nombre público, oficios, zona, calificación, número de reseñas, si está verificado, actividad reciente, señales reales de HALPII (pedidos respondidos, veces elegido, mes de alta, años de experiencia), una breve descripción y el enlace a su perfil, más oficios relacionados y un enlace para ver más. Vienen ordenados: activos hace poco, verificados, con reseñas o pedidos respondidos; quien lleva más de 45 días sin actividad solo aparece si no hay suficientes. No devuelve teléfonos ni correos: el contacto se hace desde el perfil. La ciudad es obligatoria. Los enlaces incluyen parámetros de origen (via, utm_source, utm_medium). EN: Search tradespeople in Latin America by need or trade and city; returns up to 6 public profiles with links, no contact data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ciudad": "<ciudad>"
    },
    "name": "buscar_profesionales"
  }
}

Input Schema

NameRequiredDescriptionDefault
paisNoPaís en español: «Perú», «Colombia». Opcional; ayuda si la ciudad existe en varios países
ciudadYesCiudad o distrito que dijo la persona: «Lima», «Miraflores», «Arequipa», «Cali»
limiteNoCuántos profesionales devolver (1-6)
oficioNoOficio si ya se conoce: «gasfitero», «electricista». Opcional si hay necesidad
necesidadNoLo que necesita, en sus palabras: «se fue la luz en la cocina», «pintar dos cuartos»

Output Schema

NameRequiredDescriptionDefault
paisYes
totalYesProfesionales que coinciden en HALPII (puede ser mayor que los devueltos)
ciudadYes
oficioYesOficio que HALPII dedujo de la necesidad; null si no lo reconoció
mensajeYes
necesidadYes
ver_mas_urlYesPágina web con la lista completa del oficio en la ciudad
enlace_pedidoYesEnlace para publicar un pedido y recibir hasta 3 propuestas
profesionalesYesHasta 6; muestra los 3 primeros
oficios_relacionadosYesOtros oficios que podrían servir

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations (readOnly/openWorld/idempotent/non-destructive) by disclosing the result cap of 6, the ranking logic (recent activity, verified, reviews or answered requests), the 45-day inactivity fallback, and the fact that no phone numbers or emails are returned — contact happens from the profile. It even flags that returned links carry origin parameters (via, utm_source, utm_medium), which an agent would otherwise not expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and scope, then returns, then ordering rules, then the no-contact caveat. The single dense paragraph is information-rich but long; a bulleted split between 'what it does' and 'what it returns' would scan better. Nearly every sentence carries a distinct fact, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though an output schema exists, the description covers the practically important return behaviors: field list, ordering, the 6-result cap, the inactivity fallback, and the absence of contact data. Combined with 100% schema coverage, an agent has everything needed to call it correctly and set expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter including pais, limite, oficio and necesidad is already documented. The description reinforces that ciudad is obligatory and that the limit is 6, but adds no syntax, format, or interaction detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (busca) and resource (profesionales de oficios) with an explicit scope: a city or district in Latin America, in HALPII's public directory. It is clearly distinguishable from listar_oficios (which would enumerate trades) and ver_perfil (which opens one profile), since this tool returns a ranked shortlist of up to 6 profiles with links to those profiles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating context: city is mandatory, and the query can come either as a free-form need in the person's words or as a known trade, with the tool inferring the trade. It also explains the fallback rule (profiles inactive 45+ days only appear if there aren't enough results). It never explicitly names a sibling or states when not to use it, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources