Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Code mode / bulk tool execution

Aperta
  • Qualcosa non va?
#222 1 commento 3 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
28/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Ambito
api, web-dev

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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])

Lingua principale
Bikeshed
Stelle
4.7k
Fork
328
Merge medio
2g 15h
PR unite (30g)
16

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di webmachinelearning/webmcp

Tutte le issue di webmachinelearning/webmcp

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.