Question about WebMCP and declarative API

328 views
Skip to first unread message

Raymond Camden

unread,
Feb 10, 2026, 10:56:41 AM (12 days ago) Feb 10
to Chrome Built-in AI Early Preview Program Discussions
While looking at the docs for the declarative API (https://docs.google.com/document/d/1rtU1fRPS0bMqd9abMG_hc6K9OAI6soUy3Kh00toAgyk/edit?tab=t.0#heading=h.yslvlvxa9khg), one thing seems a bit odd. I get why adding attributes to the form tag could be useful for 'announcing' that the form element is a tool, but why do we need additional parameters at the field level? Shouldn't the field names and associated labels (if used of course) provide that info? 

François Beaufort

unread,
Feb 10, 2026, 11:16:44 AM (12 days ago) Feb 10
to Raymond Camden, Chrome Built-in AI Early Preview Program Discussions
Hey Raymond,

While the browser tries to infer as much as possible from standard HTML, these extra parameters provide a "contract for interaction" that reduces hallucination and ensures the agent knows exactly how to interact with your page features.
Those HTML form elements attributes are not mandatory though. Sometimes `toolname` and `tooldescription` are all that's required.


On Tue, Feb 10, 2026 at 4:56 PM Raymond Camden <raymon...@gmail.com> wrote:
While looking at the docs for the declarative API (https://docs.google.com/document/d/1rtU1fRPS0bMqd9abMG_hc6K9OAI6soUy3Kh00toAgyk/edit?tab=t.0#heading=h.yslvlvxa9khg), one thing seems a bit odd. I get why adding attributes to the form tag could be useful for 'announcing' that the form element is a tool, but why do we need additional parameters at the field level? Shouldn't the field names and associated labels (if used of course) provide that info? 

--
You received this message because you are subscribed to the Google Groups "Chrome Built-in AI Early Preview Program Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chrome-ai-dev-previe...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chrome-ai-dev-preview-discuss/0aeb7160-5b50-406d-b12e-6e8b58bd14d5n%40chromium.org.

Raymond Camden

unread,
Feb 11, 2026, 10:24:04 AM (11 days ago) Feb 11
to François Beaufort, Chrome Built-in AI Early Preview Program Discussions
Thanks for the reply. As a quick aside, I apologize, I did read but rather quickly, and missed that the input elements name is used by default, and the associated label is used as well. It does exactly what I think I should - and I should not read specs before coffee. 
--
===========================================================================
Raymond Camden

Email : raymon...@gmail.com
Blog : www.raymondcamden.com

Reply all
Reply to author
Forward
0 new messages