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

Reserve an extension member on tools and results, like MCP's `_meta`

Abierto
  • ¿Algo no está bien?
#354 0 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript
Área
api

Línea de trabajo

Start by reading the ModelContextTool and RegisteredTool definitions in the WebMCP specification, then review the linked discussions #9, #41, #73, #255, #271, and #282 for related decisions. The issue proposes a new extension point but leaves its name, size limits, and filtering behavior open; done would require resolving those design questions and updating the spec.

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

Descripción

Summary

MCP lets tools, results and requests carry extra data in a _meta member. Specs and products built on top of MCP have used that to try ideas without waiting for the core spec: links from a tool to a UI resource, tool visibility, short status strings while a tool runs, and vendor extensions. WebMCP's ModelContextTool and ToolAnnotations are fixed sets of members, so an experiment has nowhere to go except new annotations in the core spec.

Why it is useful

  • WebMCP is young and is still being shaped by implementers in the origin trial. Experiments that need a field (a display string for a running tool, a pointer to a longer description, a grouping hint such as #255 or #271) currently need a spec change first, or live in the description text where agents may read them as instructions.
  • #41 mentions deferring annotations and _meta on image results, so the question has come up already.
  • When an experiment works, it can be promoted to a real member with real semantics. MCP has done this repeatedly.

Proposal

A reserved, optional member (name up for discussion) on ModelContextTool and RegisteredTool, and on results if results become typed (#9, #41, #282):

  • user agents ignore it;
  • keys should be prefixed (reverse-DNS or a short vendor name) to avoid collisions, as MCP recommends for _meta;
  • the data is supplied by the page, so agents should treat it as untrusted, and should not show it to a model unless they choose to. It is not a place for instructions;
  • it is carried to extensions and agents like the rest of the descriptor.

What I'm not proposing

No new behaviour and no new capabilities. Only a place for data that the platform does not interpret.

Open questions

  • Whether size limits should apply (see #73 on input lengths).
  • Whether exposedTo filtering applies to the whole descriptor, which I would assume.
Lenguaje dominante
Bikeshed
Estrellas
4.7k
Forks
328
Merge medio
1 d 21 h
PR fusionados (30 d)
15

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.