mistral_openapi_client/models/mcp_tool_call_response.rs
1/*
2 * Mistral AI API
3 *
4 * Our Chat Completion and Embeddings APIs specification. Create your account on [La Plateforme](https://console.mistral.ai) to get access and read the [docs](https://docs.mistral.ai) to learn how to use it.
5 *
6 * The version of the OpenAPI document: 1.0.0
7 *
8 * Generated by: https://openapi-generator.tech
9 */
10
11use crate::models;
12use serde::{Deserialize, Serialize};
13
14/// McpToolCallResponse : Response from calling an MCP tool. We override mcp_types.CallToolResult because: - Models only support `content`, not `structuredContent` at top level - Downstream consumers (le-chat, etc.) need structuredContent/isError/_meta via metadata SYNC: Keep in sync with Harmattan (orchestrator) for harmonized tool result processing.
15#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
16pub struct McpToolCallResponse {
17 #[serde(rename = "content")]
18 pub content: Vec<models::Content5Inner>,
19 #[serde(rename = "metadata", default, with = "::serde_with::rust::double_option", skip_serializing_if = "Option::is_none")]
20 pub metadata: Option<Option<models::McpToolCallMetadata>>,
21}
22
23impl McpToolCallResponse {
24 /// Response from calling an MCP tool. We override mcp_types.CallToolResult because: - Models only support `content`, not `structuredContent` at top level - Downstream consumers (le-chat, etc.) need structuredContent/isError/_meta via metadata SYNC: Keep in sync with Harmattan (orchestrator) for harmonized tool result processing.
25 pub fn new(content: Vec<models::Content5Inner>) -> McpToolCallResponse {
26 McpToolCallResponse {
27 content,
28 metadata: None,
29 }
30 }
31}
32