ComplyEdge TrustLint
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_complianceA | EU AI Act Article 5 and Article 50. TrustLint offline regex: not the hosted policy engine, not a system classifier. Check already-produced text (model input or output) against ComplyEdge TrustLint offline YAML rules (regex corpus). Use for post-hoc evaluation of text that already exists; for pre-generation screening of a prompt about to be sent, use scan_prompt. Argument |
| list_rulesA | EU AI Act Article 5 and Article 50. TrustLint offline regex: not the hosted policy engine, not a system classifier. List TrustLint offline compliance rules in the ComplyEdge corpus : the discovery tool; returns no PASS/FAIL or SAFE/RISK verdict. Use it to scope a jurisdiction before calling check_compliance; do not use it to evaluate text. Optional |
| scan_promptA | EU AI Act Article 5 and Article 50. TrustLint offline regex: not the hosted policy engine, not a system classifier. Scan an AI prompt with ComplyEdge TrustLint offline YAML rules (regex corpus) before generation : pre-generation only. Use when the prompt is about to be sent; for post-hoc evaluation of already-produced text, use check_compliance. Argument |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
list_rules is clearly a discovery tool distinct from the two scanners. check_compliance and scan_prompt run the same regex corpus on different inputs (already-produced text vs. a prompt about to be sent), and both descriptions explicitly point to each other; the lifecycle distinction is clear but the underlying operation is nearly identical, so some misselection is possible.
All three tools use a consistent snake_case verb_noun pattern: list_rules, check_compliance, scan_prompt. The convention is predictable and readable throughout.
Three tools is minimal but well-scoped for an offline regex linter: one discovery tool and two evaluation modes (post-hoc vs. pre-generation). Each tool has a clear role, though the surface is slightly thin for a compliance domain.
The surface covers rule discovery and evaluation for both prompts and generated text, which are the core workflows. Minor gaps exist, such as no tool for retrieving detailed rule content or batch/aggregate scanning, but agents can work around these.