Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

How do agent handle pre-filled or user-modified form values?

Abierto
  • ¿Algo no está bien?
#157 0 comentarios 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
html
Área
api

Línea de trabajo

Start by reading the WebMCP specification sections that define form tools and their input schemas; this issue does not name specific files or tests. Compare the two proposed approaches for exposing current form values and determine whether the specification should define a mechanism. Done means the specification question has a resolved direction and the corresponding behavior is clearly specified.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

declarative

Agents currently lack a reliable mechanism to invoke a tool based on a WebMCP form that contains values either manually filled by the user or pre-populated by the website. The agent is unaware of the form's current state, meaning it cannot confidently fulfill a user instruction like, "Submit this form. Trust me, I've already filled those fields". The agent is forced to rely solely on the schema defined by the form tool itself.

If an input field is marked as required, the agent cannot submit the form because it does not know the current value, effectively blocking the submission even if the form is valid in the browser.

<form toolname="submit_form" tooldescription="Submit form">
    <input type="text" name="name" value="John Doe" required>
    <button>Submit</button>
</form>

- User: Submit this form
- Agent: I can do that. What is the name of the form you would like to submit?

If the required attribute is omitted (or not by the way), the agent may "hallucinate" and generate a random value for the field rather than using the pre-filled value, potentially leading to the submission of incorrect data.

- User: Submit this form
- Agent: Call "submit_form" with {"name":"default_form"}

Ideally, the agent should have a method to submit the form using its current, visible values, despite some fields being required. We should clarify if the WebMCP specification should have a mechanism for this. We could either:

  1. Allow the agent to "read" the form values directly from the DOM.
  2. Mandate that the WebMCP specification requires exposing additional tools for each declared form tool, where these additional tools return the current form field values.
Lenguaje dominante
Bikeshed
Estrellas
4.7k
Forks
328
Merge medio
2 d 15 h
PR fusionados (30 d)
16

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de webmachinelearning/webmcp

Todos los issues de webmachinelearning/webmcp

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.