Home/llm-observability-mcp
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(config): update observability rules in readme

Browse Source 
Update the README.md to include detailed instructions for llm_observability_otel tool usage, specifying required parameters and system prompt requirements. The changes clarify the observability implementation guidelines and ensure consistent operation naming.
This commit is contained in:
Stefano Fiorini
2025-07-15 20:14:30 -05:00
parent d4fd61a344
commit 7b35d74659
1 changed files with 12 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@@ -177,8 +177,17 @@ alwaysApply: true
## Rules ## Rules
- Run llm_observability_otel tool for each interaction. ---
- Each request should instruct the LLM to include instruction to run the llm_observability_otel within the response. description: llm_observability_otel
globs: *
alwaysApply: true
---
## Rules
SYSTEM PROMPT:
- When the user asks anything, output a llm_observability_otel tool invocation in valid MCP JSON.
- Repeat tool invocation until success invocation.
- Make sure to include all parameters below unless they are optional and you have no value for them. - Make sure to include all parameters below unless they are optional and you have no value for them.
- You need to gather the following parameters: - You need to gather the following parameters:
- userId - The distinct ID of the user - userId - The distinct ID of the user
@@ -197,6 +206,7 @@ alwaysApply: true
- errorType - Type of error (e.g. rate_limit, timeout, etc.) - errorType - Type of error (e.g. rate_limit, timeout, etc.)
- mcptoolsUsed - List of MCP tools used by the interaction - mcptoolsUsed - List of MCP tools used by the interaction
- For the userId send stefano.fiorini. - For the userId send stefano.fiorini.
- For outputChoices send the full response text from the LLM
- For the operationName a three words separated by underscore identifying the conversation. - For the operationName a three words separated by underscore identifying the conversation.
- All interactions within the same conversations should be sent with the same operationName. - All interactions within the same conversations should be sent with the same operationName.
``` ```