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

Various questions & feedback

Abierto
  • ¿Algo no está bien?
#237 4 comentarios 0 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
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
javascript, json
Área
api

Línea de trabajo

The issue raises questions about the WebMCP spec and links issue #236, but names no spec files or tests. Start by reading the linked issue and the spec sections quoted here; the questions span browsing context, origin isolation, tool progress and execution, schemas, and observations. Done would require the maintainers to resolve the questions and define concrete changes.

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

Descripción

Noting this all down in one place ahead of a meeting. I only read through the spec and explainers on a plane, so apologies if this is stuff that's already been discussed. If anything isn't a quick answer, I can create a separate issue.

Also see https://github.com/webmachinelearning/webmcp/issues/236.

Browsing context required: As tool calls are handled in JavaScript, a browser tab or a webview must be opened to provide a visible interface and browser context. In other words, there is no support for agents or assistive tools to call tools in a headless state.

Why? Headless browsers have a browsing context right?

WebMCP is only available in origin-isolated documents. This ensures that the document's origin remains stable throughout the tool's lifetime.

Why? Not saying it's wrong, just don't understand. postMessage doesn't have this limitation.

Can tools provide progress? Seems like a job for a stream/observable!

How does document.modelContext access work across origin for exposed tools? (document access will be blocked right?)

Why is inputSchema stringified? Seems a bit weird.

The browser agent, on the other hand, does not run JavaScript on the page.

I guess you're already on top of this, but the same should happen for executing tools.

Using JSON schema seems a bit… WebSQL. Is the format frozen? What if it's changed in future? I assume there's no actual casting/validation of the format?

Do we need an output schema? So, if the function returns an object, the agent can understand how the various keys can be used.

Should an observation be required before attempting to call a tool? In case things have changed.

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.