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

Code mode / bulk tool execution

Abierto
  • ¿Algo no está bien?
#222 1 comentario 3 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
28/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Área
api, web-dev

Línea de trabajo

Start with the Pizza Maker demo, its individual WebMCP tools, and the proof of concept linked in the issue. Review WebMCP's tool and spec extension points to determine where bulk execution and tool annotations would belong. Done means agreeing on a concrete API and specification change, then implementing them with examples and tests; the issue currently leaves implementation location and requirements unresolved.

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

Descripción

enhancement

Code mode or code execution with MCP is a concept that was more broadly shared late last year:

https://www.anthropic.com/engineering/code-execution-with-mcp
https://blog.cloudflare.com/code-mode/

I was wondering how this concept could be applied to WebMCP so I was tinkering with it over at https://github.com/GoogleChromeLabs/webmcp-tools/pull/287

The idea is simple: instead of (or in addition to) exposing every single WebMCP tool to an agent, there's a single execute_tools tool that allows the agent to execute N tools in one go.

Let's take this Pizza Maker demo as an example. To create a pizza, you'd normally call tools such as set_pizza_size, set_pizza_style, and add_topping one after the other. That's a lot of roundtrips and a lot of tokens. The same task with execute_batch could be accomplished with a single tool call execute_tools([set_pizza_size, set_pizza_style, add_topping]).

Early testing shows greatly reduced number of roundtrips, token usage, and increased speed. Which is why I think this could be really interesting for both website developers as well as the agent developers. Such an execute_tools function could be implemented on either side.

Of course this works best for more deterministic scenarios that don't involve dynamic tool additions or page navigations. So it made me wonder how the WebMCP spec could help in this case. For example with a new ToolAnnotation to mark tools suitable for this kind of batching. (See also #176). Or a way to define meta tools such as make_pizza, which under the hood would be execute_tools([set_pizza_size, set_pizza_style, add_topping])

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.