Skip to main content
Glama

Preparar enlace de pedido

crear_enlace_pedido
Read-onlyIdempotent

Arma un enlace a portal.halpii.com/solicitar con el oficio y la ciudad ya llenos. No publica nada, no envía datos y no recibe datos personales. La persona abre el enlace, confirma su pedido en el portal (ahí deja su contacto) y recibe hasta 3 propuestas de profesionales de su zona. El enlace incluye parámetros de origen (via, utm_source, utm_medium). EN: Only builds a prefilled link to HALPII's request form; nothing is submitted and no personal data is collected.

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": {
      "oficio": "<oficio>",
      "ciudad": "<ciudad>"
    },
    "name": "crear_enlace_pedido"
  }
}

Input Schema

NameRequiredDescriptionDefault
ciudadYesCiudad o distrito que dijo la persona: «Surco»
cuandoNoPara cuándo: «hoy», «esta semana» (no se envía)
oficioYesOficio o necesidad: «gasfitero», «arreglar una fuga»
descripcionNoQué necesita (no se envía; se devuelve para que la persona lo escriba en el formulario)

Output Schema

NameRequiredDescriptionDefault
urlYes
ciudadYes
oficioYes
mensajeYes
prellenadoYesCampos que el formulario recibe ya llenos
para_copiarYesDetalles que la persona debe escribir ella misma en el formulario
oficio_reconocidoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses that nothing is published, nothing is sent, no personal data is received, and that "cuando" and "descripcion" are not transmitted but returned so the person can type them into the form. It also mentions origin parameters (via, utm_source, utm_medium) that the schema does not expose, which is useful but slightly under-explained since additionalProperties is false.

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

Conciseness5/5

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

The definition leads with what gets built, then immediately handles the privacy/no-op concern, then the downstream flow. The bilingual EN line is a short restatement rather than bloat, and no sentence is filler.

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

Completeness4/5

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

An output schema exists so return values need no explanation, and the description covers the side-effect profile and human handoff completely. The only loose end is the origin/UTM parameters that appear in prose but not in the input schema, which an agent could find mildly ambiguous.

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%, so the parameter meanings are already fully documented, including the "no se envía" notes. The description only restates that oficio and ciudad are prefilled in the link and adds the UTM/origin detail, which is marginal added meaning over the schema; baseline 3 applies.

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

Purpose4/5

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

The description uses a concrete verb and resource: it builds a prefilled link to portal.halpii.com/solicitar with "oficio" and "ciudad" already populated, and it clarifies that nothing is submitted. That makes the purpose unmistakable and clearly different in spirit from the sibling search/profile tools, though it never names a sibling to make the boundary explicit.

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?

It gives clear usage context: the person opens the link, confirms the request in the portal where they leave their contact, and receives up to 3 proposals from local professionals. It does not explicitly say when to prefer this over a sibling tool or name any exclusion, so it stops short of the top band.

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