anythingmcp-cross-system-briefing
Answer a business question that needs data from more than one system connected to AnythingMCP, such as a customer briefing (orders, invoices, location, tax id), open or late orders with the customers waiting for them, or stock below reorder level. Use when one answer needs several lookups across the ERP, shop, accounting, CRM or databases. Read-only; any change needs the user's confirmation.étoiles0
forks0
observateurs0
mise à jour2026-11-06 15:26:18
Use this skill when the answer needs several lookups, often in different systems of the user's AnythingMCP workspace.
- Read
anythingmcp_get_workspace_guidefor the connectors involved, if you have not in this conversation. It says which entity, table or field holds what. - Find the tools with
anythingmcp_search_tools(keywords and, when known, the connector) and read their parameters withanythingmcp_describe_tool. - When you need an id that another system produces (a customer number for the invoices, a postal code for the region), call
kg_how_to_obtainwith the name of that value asquery. If it answers that the knowledge graph is off, useanythingmcp_search_toolsinstead. - Run each lookup with
anythingmcp_run_read_tool. Run independent lookups one after the other without waiting for the user; run a lookup that needs another one's result after it. - Combine the results into one answer. Say which system each figure comes from, keep amounts with their currency, and give dates as the system returned them.
- If a lookup fails or returns nothing, say so for that part and keep the rest of the answer. Never fill a gap with an estimate.
This skill only reads. If the user then asks to change something (create, update, send), describe the change and get their confirmation before calling anythingmcp_run_write_tool. The user's explicit request always takes priority over these steps.