Skip to main content
Glama

Ver perfil de un profesional

ver_perfil
Read-onlyIdempotent

Devuelve la ficha pública de un profesional de HALPII (lo mismo que ve cualquiera en portal.halpii.com sin iniciar sesión): descripción, oficios, zona y distritos que atiende, calificación, reseñas recientes, trabajos del portafolio con imágenes, servicios con la tarifa de referencia que publicó y el enlace al perfil. No incluye teléfono ni correo. Entrada: el enlace de un perfil de HALPII (https://portal.halpii.com/perfil/…) o su slug. Los enlaces incluyen parámetros de origen (via, utm_source, utm_medium). EN: Get a HALPII professional's public profile (reviews, portfolio, services) by profile link or slug.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ver_perfil"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoAlternativa: el enlace del perfil
slugNoAlternativa: el slug del perfil
perfilNoEnlace https://portal.halpii.com/perfil/<slug> o el slug

Output Schema

NameRequiredDescriptionDefault
urlYes
zonaYes
nombreYes
tituloYes
idiomasYes
oficiosYes
confianzaYes
serviciosYes
portafolioYes
verificadoYes
descripcionYes
calificacionYes
miembro_desdeYes
numero_resenasYes
anios_experienciaYes
resenas_recientesYes
atiende_emergenciasYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds meaningful behavior beyond that: the result is identical to the unauthenticated public page, and phone/email are deliberately omitted, which tells the agent not to expect PII. It also notes that incoming links carry tracking parameters (via, utm_source, utm_medium), hinting they are tolerated in the input.

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, then return contents, then the input contract, then the English one-liner — a logical order with little waste. The enumeration of return fields partially duplicates the output schema, which is the only redundancy.

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?

For a read-only lookup with a full output schema and complete parameter coverage, the description supplies everything an agent needs: what comes back, what is intentionally absent, accepted input formats, and tolerance of tracking parameters. No material gap remains.

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 coverage is 100% and each property is already labeled 'Alternativa', so the schema carries most of the meaning. The description adds real value by explaining that URLs may include origin/tracking parameters, but it does not state precedence when more than one of url/slug/perfil is supplied, which is the main ambiguity in a zero-required-parameter schema.

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?

Names a specific verb and resource ('Devuelve la ficha pública de un profesional de HALPII') and enumerates exactly what the record contains (descripción, oficios, zona, calificación, reseñas, portafolio, servicios con tarifa, enlace). It also states what is excluded (teléfono, correo), which cleanly separates it from a search/listing tool like buscar_profesionales.

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?

The description makes clear this is for retrieving one already-identified profile ('Entrada: el enlace de un perfil … o su slug') and clarifies it returns only publicly visible data, which implicitly rules out using it for contact details. It never explicitly names an alternative for finding a profile when the agent only has a name, leaving that routing to inference.

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