Conversation
github-actions
bot
added
the
feature definition
|
Tests will pass once w3c/browser-specs#2365 is resolved. |
beaufortfrancois
force-pushed
the
main
branch
from
3c00dea to
a35a493
Compare
ddbeck
left a comment
ddbeck
left a comment
There was a problem hiding this comment.
Thanks for filing the issue and opening this PR. I have a suggestion for the description to follow our conventions, but otherwise this is close to done.
(We can override the spec URL check if we finish before the browser-specs update lands here.)
| @@ -0,0 +1,3 @@ | |||
| name: WebMCP | |||
| description: Exposes structured tools for AI agents on existing websites. | |||
There was a problem hiding this comment.
I am suggesting describing this in terms of entrypoints: what named thing does a developer invoke to bring about what consequence? I've ended up here:
| description: Exposes structured tools for AI agents on existing websites. | |
| description: The `navigator.modelContext` API registers functions to be called by tools external to the page, such as browser extensions or in-browser generative AI models. |
That said, I feel like this is a little speculative, since the spec is quite incomplete and the other links given in the issue don't really explain what the API does (as opposed to tools that might call upon its registry).
There was a problem hiding this comment.
This is actually more than that. WebMCP provides JavaScript and annotates HTML form elements so that agentic browsers know exactly how to interact with page features to support a user's experience.
There was a problem hiding this comment.
Ah, interesting! Do you know what the likely method for annotations will take? Is it an API or HTML attributes or something else?
There was a problem hiding this comment.
HTML form attributes like toolname and tooldescription. See webmachinelearning/webmcp#76
2 participants
FIX #3777