> For the complete documentation index, see [llms.txt](https://docs-en.dmflow.chat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-en.dmflow.chat/domain/chat/gossip-tools.md).

# Role-Chat Tools

What is Role-Chat? Role-chat integrates Document Q\&A and Form Q\&A.

How to find domain\_id and table\_id for reference? Most will have auto-suggestion functionality, but some newer tools may not.

How to find domain\_id

How to find table\_id

search\_table:

* domain\_id: Select the domain of the form (must be Form Q\&A).
* table\_id: Select the ID of the form.
* You can query the form content via "SQL". The searched content is based on visitor permissions. You can go to Form Permissions and integrate CARD output.

Card Output:

* You can map the searched content to the corresponding fields and use 'Preview' to preview.

rate\_conversation:

* Determines if the customer intends to leave and asks the customer if the conversation was "helpful" or "not helpful". This will be automatically logged.

search\_knowledge:

* domain\_id: Select the domain of the form (must be Document Q\&A).
* description: Describe the search term.
* This tool automatically calls the Document Q\&A content for answering.

collect\_user\_info:

* username
* email
* phone
* Set the above to true to allow the bot to update user information based on user conversations.

create\_table\_data:

* domain\_id: Select the domain of the form (must be Form Q\&A).
* table\_id: Select the ID of the form.
* trigger\_id: Trigger ID.
* Use this tool to add form content. Calling this tool does not require setting form permissions; insertion permissions are sufficient. After successful insertion, the trigger will be called.

human\_agent\_help:

* Use this tool when a user needs live agent help. It will automatically fallback and log the visitor's question in the shared notes.

auto\_suggestion:

* Use this tool to automatically add up to three recommended user queries.

googlemap\_routes\_api:

* api\_key: Encrypt the API key in the settings first, then enter it.
* limit: The original maximum is 25; you can set it to 1-25. It will filter the closest distances via straight-line distance calculation before calling this API.

Encryption API KEY Location:

custom\_service:

* Allows you to call your own API, but the payload cannot exceed 4K (CJK characters count as 1, other languages approximately 3-5 letters per length 1).
* resource\_id: Resource ID.
* name: functionName (equivalent to the name of the LLM calling tool).
* description: function Description (equivalent to the description of the LLM calling tool).
* parameters: {name: string, description: string, type: 'string' | 'number' | 'boolean' | 'string\_array', require: boolean, enums: string}.
* Parameter section, only supports string, number, boolean, and string array. Object array is currently not supported. Enums can be separated by '|', for example: Chinese|English|Japanese. Resource nodes will be introduced later.

suggestion\_items:

* Uses the built-in product search function.

search\_reserve\_range:

* You must first select a form with a reservation component to use this function.
* domain\_id
* table\_id
* description: Allows the LLM to understand what object you want to reserve.

collect\_user\_tag:

* Use this tool to collect visitor tags. If the tag name exists in the visitor's tags, it will be added.
* {name: string, description: string}\[]

get\_form\_link:

* Retrieves the external link for inserting a form component, binding the visitor's identity.
* array name, description, table\_id

code\_geodesic:

* Uses code to determine latitude and longitude distance.

store\_memory:

* Allows you to store, query, and remove visitor persistent memory.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs-en.dmflow.chat/domain/chat/gossip-tools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.