feat: [ECO-515] - Add traces to MCP server

[YassineGabsi]

No description provided.

[ArzelaAscoIi]

tests ? 😬

Code looks good :)

[Copilot]

Pull request overview

• Adds MCP tools and API client support for retrieving Haystack pipeline run traces (list + single trace) within a workspace/pipeline context.

Changes:

• Introduces list_pipeline_traces and get_pipeline_trace tool wrappers in src/deepset_mcp/tools/search_history.py.
• Adds corresponding API resource methods + protocol surface in src/deepset_mcp/api/search_history/.
• Registers the new tools in the MCP tool registry.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/deepset_mcp/tools/search_history.py	Adds new user-facing MCP tools for listing traces and fetching a single trace.
src/deepset_mcp/mcp/tool_registry.py	Registers the new tools so they are exposed by the MCP server.
src/deepset_mcp/api/search_history/resource.py	Implements API calls for listing traces and retrieving a single trace.
src/deepset_mcp/api/search_history/protocols.py	Extends the resource protocol with the new trace-related methods.
src/deepset_mcp/api/search_history/models.py	Introduces trace-related Pydantic models (PipelineTraceEntry, Haystack trace schema models).
src/deepset_mcp/api/search_history/__init__.py	Exports new trace models from the search history API module.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[YassineGabsi]

@ArzelaAscoIi I added more tests, and I reshaped a bit the Search history one as well since it was outdated, can you please check again ? thanks 🙏🏻