Wayki

Showing 25 of 38 from the live probe.

• List Wayki projects

  Lists the Wayki projects the signed-in user belongs to. Use it first to turn a project name into the id every other tool needs.

• List project members

  Lists who belongs to the project, with their name, email and role. Use it to answer "quién está en el proyecto" and whenever the user names a person you have not seen yet — the write tools accept names, but knowing the roster lets you spot an ambiguity before proposing anything.

• List project groups

  Lists the teams (grupos) configured in the project, with how many people each one covers. A group can hold an assignment exactly like a person can, so call this when the user names a team — "el grupo de oficina técnica" — and you need to be sure it exists before proposing the change. The write tools accept group names directly; this is what lets you spot an ambiguity first.

• List valid issue filter values

  Returns the statuses, priorities and categories configured for a project. These are defined per project, so call this before filtering if a label is not obvious.

• List issues

  Lists issues in a Wayki project. Status, priority and category accept human labels ("Abierto", "Crítica") or canonical groups ("open", "critical"). Results already respect the user permissions: a plain member only sees issues they report, are assigned to, or observe.

• Get one issue

  Returns the full detail of a single issue, optionally with its replies and change history.

• Issue statistics

  Project-wide issue metrics: totals, open/closed/overdue counts, distribution by status and priority, and the most loaded assignees.

• List RFIs

  Lists RFIs (requests for information) in a Wayki project. Status, priority and type accept human labels ("Abierta", "Alta") or canonical groups ("open", "high"); each filter takes a single value because the API does. Results already respect the caller permissions.

• Get one RFI

  Returns the full detail of a single RFI: status, assignees, due date, description and the answer if it has one.

• List change orders

  Lists change orders (órdenes de cambio) with their cost and schedule impact. Use it for questions about scope changes, adicionales, or budget impact of approved changes. Sort by costImpact.amount to rank them.

• List planning tasks

  Lists schedule tasks (Gantt / lookahead) in a Wayki project. Status and priority accept human labels or canonical groups. Date windows filter start and end dates, which is how you answer "what finishes this month" or "what is late".

• List planning constraints

  Lists the constraints (restricciones) blocking schedule tasks, with who owns each one and whether it is already cleared. Use it for lookahead / Last Planner questions such as "what is blocking us".

• List meetings

  Lists project meetings with their participants and the agreements (acuerdos) taken in each one. `from`/`to` window the planned start date, so use them for "meetings this week" or "last month". Status and priority are fixed enums here, not per-project labels.

• List commitments (meeting agreements)

  Cross-meeting commitments (acuerdos) as addressable records: what was promised, who is responsible, when it is due and whether it was complied — across ALL meetings, without walking them one by one. Use it for "¿qué compromisos hay pendientes?", "¿qué venció?", "¿qué debe fulano?" or before a weekly coordination. Prefer this over wayki_list_meetings when the question is about commitments, not meetings.

• List site plan pins

  Lists the pins placed on a site floor plan (planos de obra, puntos 360°). Pins belong to one plan: call it without siteId to get the plans and their ids, then again with the one you want.

• Project overview

  One-shot snapshot of a project: issue counts (open / closed / overdue and the top priorities), RFI counts, task counts, and what was created in the last 7 days. Prefer this over several list calls when the user asks about overall status, KPIs, health or 'how is the project going'.

• My agenda

  The signed-in user's own workload in a project: issues, RFIs and tasks assigned to them that are overdue or due within the next N days. Use it for 'what's on my plate', 'qué tengo pendiente', 'mi agenda'. It never reports other people's work.

• Search across modules

  Keyword search over issues, RFIs, tasks and meetings of one project in a single call. Use it when the user does not say which module ("busca el tema de la losa"); prefer the specific list tools when they do.

• Chart data

  Aggregates one dataset of the project into a ready-to-plot chart payload. Use it when the user asks for a chart, a graph or a visual breakdown. `dataSource` is a closed catalogue and it carries the grouping: there is no separate "group by" argument, so `rfis_by_priority` means "RFIs, counted by priority". **If the grouping the user asked for is not on the list, say so instead of charting a different one** — the chart is titled by the server after the dataset you picked, so a substitution shows u

• Budget summary

  Cost KPIs for the project budget: direct and indirect totals, how many line items, and optionally the biggest ones. Use it for questions about presupuesto, costo, APU or partidas.

• Analyze model revision impact

  Analyzes the latest BIM model revision of a project (or a specific diff): what elements were added / deleted / modified, and which issues, RFIs, schedule activities and budget items are linked to the changed elements. Use it when the user asks about a new model version, "qué cambió en el modelo", or the impact of a design change.

• List attention items (Risk Center)

  Open findings of the project's Risk Center: model-change impacts, anomalies and other items that need human attention, each with evidence and severity. Use it for '¿qué requiere mi atención?', 'riesgos del proyecto', or as the first call of a morning status check.

• RFI risk ranking

  Open RFIs ranked by a deterministic composite risk score (0-100): SLA/overdue, age, linked model elements, and — via the 4D links and the CPM solver — whether they block in-progress, low-float or critical-path activities. Every score comes with its explainable factors. Use it for "¿qué RFIs son los más riesgosos?", "¿algún RFI puede retrasar la obra?", or before a coordination meeting.

• Field progress vs plan (planned vs actual)

  Observed field progress per activity (human readings, often with 360-capture evidence) compared against the linear plan of each activity's dates — worst gaps first, alongside what planning self-reports. Use it for "¿cómo va el avance real en campo?", "¿qué actividades están atrasadas de verdad?", or before a weekly review. Empty means nobody has recorded field observations yet.

• Entities by project attribute

  Issues, RFIs, órdenes de cambio, formularios, actividades y reuniones etiquetados con un PROJECT ATTRIBUTE (Especialidades, Niveles, Sectores…). Estos atributos son una taxonomía DISTINTA de las categorías de issues. Sin `attribute`: catálogo de atributos y sus valores. Con `attribute` sin `value`: conteo de uso por valor. Con ambos: la lista de entidades. Si el usuario usa lenguaje natural ("eléctricas"), pide primero los valores y mapea al label real del proyecto (p. ej. IIEE) — la tool respon