MCP tools: choose what the AI Agent reads from a tool result

MCP: create knowledge sources and file articles into them

An AI assistant connected over the MCP server can now create a knowledge source and file the articles it writes into that source. A batch of imported documents then appears on the Knowledge page as one source instead of loose articles under Created in Ada.

What’s new

Create a source: edit_agent_config accepts a knowledge_source entity with name, optional external_id, and optional metadata. Create only; rename and delete stay in the Knowledge API.
List sources: list_entities accepts entity_type='knowledge_sources' and returns each source’s Ada id, Knowledge API external_id, and deletion status.
File an article into a source: edit_agent_behavior accepts knowledge_source_id on knowledge article created and modified changes. Sources that hold imported articles, are managed by an integration, are a website import, or are being deleted are refused.
Dashboard keeps Edit and Delete: articles written in Ada stay editable in the dashboard whichever source they are filed under, and saving one no longer moves it back to Created in Ada.

MCP tools: choose what the AI Agent reads from a tool result

Each MCP tool now has a What the AI Agent reads setting. Full tool result stays the default: the Agent reads the whole result your server returned. Only the output variables limits the Agent to the outputs you saved as variables, returned as one JSON object under their output names.

Use Only the output variables to keep a large or noisy result out of the conversation. The response size limit then applies to the outputs you defined, not to the whole result. The option needs at least one saved output.

The Tools API exposes the same choice as mcp.llm_reads on MCP tools, with values full_result and mapped_outputs.

To learn more, see What the AI Agent reads.