You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: capabilities/conversational_search/advanced/chat_tooling_reference.mdx
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,10 @@ description: An exhaustive reference of special chat tools supported by Meilisea
5
5
6
6
When creating your conversational search agent, you may be able to extend the model's capabilities with a number of tools. This page lists Meilisearch-specific tools that may improve user experience.
7
7
8
+
<Note>
9
+
In code examples, replace `WORKSPACE_NAME` with the name of your workspace. On Meilisearch Cloud, the default workspace name is `cloud`.
10
+
</Note>
11
+
8
12
## Meilisearch chat tools
9
13
10
14
For the best user experience, configure all following tools.
@@ -112,6 +116,7 @@ curl \
112
116
-H 'Content-Type: application/json' \
113
117
--data-binary '{
114
118
"model": "PROVIDER_MODEL_UID",
119
+
"stream": true,
115
120
"messages": [
116
121
{
117
122
"role": "user",
@@ -145,7 +150,7 @@ curl \
145
150
"parameters": {
146
151
"type": "object",
147
152
"properties": {
148
-
"role": { "type": "string", "description": "The role of the messages author, either user or assistant" },
153
+
"role": { "type": "string", "description": "The role of the messages author, either `tool` or `assistant`" },
149
154
"content": { "type": "string", "description": "The contents of the assistant or tool message. Required unless tool_calls is specified." },
150
155
"tool_calls": {
151
156
"type": ["array", "null"],
@@ -183,7 +188,7 @@ curl \
183
188
"type": "object",
184
189
"properties": {
185
190
"call_id": { "type": "string", "description": "The call ID to track the original search associated to those sources" },
186
-
"documents": { "type": "object", "description": "The documents associated with the search. Only displayed attributes are returned" }
191
+
"documents": { "type": "array", "items": { "type": "object" }, "description": "The documents associated with the search. Only displayed attributes are returned" }
187
192
},
188
193
"required": ["call_id", "documents"],
189
194
"additionalProperties": false
@@ -223,7 +228,7 @@ const tools = [
223
228
parameters: {
224
229
type:'object',
225
230
properties: {
226
-
role: { type:'string', description:'The role of the messages author, either user or assistant' },
231
+
role: { type:'string', description:'The role of the messages author, either `tool` or `assistant`' },
227
232
content: { type:'string', description:'The contents of the assistant or tool message.' },
Copy file name to clipboardExpand all lines: capabilities/conversational_search/advanced/reduce_hallucination.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ When Meilisearch sends retrieved documents to the LLM, the model may:
14
14
- Combine facts from different documents in incorrect ways
15
15
- Generate plausible-sounding but fabricated details
16
16
17
-
The key principle is: **the LLM should only use information from the documents Meilisearch retrieves, never its general knowledge**. All the techniques below reinforce this principle.
17
+
The key principle is: **the LLM should only use information from the documents Meilisearch retrieves, not its general knowledge**. By default, LLMs may draw on their training data to fill gaps. All the techniques below help enforce this boundary and keep responses grounded in your indexed data.
0 commit comments