Skip to content

Define Declarative WebMCP integration with form-associated custom elements #94

@beaufortfrancois

Description

@beaufortfrancois

We need to define how declarative WebMCP handles form-associated custom elements:

  • Do we introduce a new setToolSchema() on ElementInternals to set their input schema?
  • How can toolparamtitle and toolparamdescription be used?
  • How do we notify the custom element when data needs to be filled due to a tool execution? What happens it it takes too long?
  • Do they also need a name to be valid?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions