ag-ui-protocol / ag-ui-protocol/ag-ui

[Feature]: Support for outputSchema in Tool interface

Abierto
#1,519 0 comentarios 0 reacciones 0 asignados Ver en GitHub
enhancement
Lenguaje dominante
Python
Estrellas
15.9k
Forks
1.4k
Merge medio
1 d 17 h
PR fusionados (30 d)
163

Descripción

### Pre-flight Checklist

- [x] I have searched existing issues and this hasn't been requested yet.

### Problem or Motivation

Hello,

It is possible in [MCP tools](https://modelcontextprotocol.io/specification/2025-06-18/server/tools#tool) to provide both an input schema and an [output schema](https://modelcontextprotocol.io/specification/2025-06-18/server/tools#output-schema).

But the [`Tool` interface](https://github.com/ag-ui-protocol/ag-ui/blob/b80612d9bd7a25a13df3aaa751ff048dfe5b8c7a/sdks/typescript/packages/core/src/types.ts#L186-L191) exposed by AG-UI:
- does not use the same property names as the MCP spec
- in particular, does not support `outputSchema`

Would it be possible to add support for `outputSchema` ? I believe this could be useful to let the LLM know what it can expect as output of a given tool call.

Also, why not align on the MCP spec ?

Thank you !

### Proposed Solution

Align on the MCP spec for tools, and in particular support `outputSchema`.

### Alternatives Considered

_No response_

### Additional Context

_No response_

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.