Skip to main content
Glama
ComplyEdge

ComplyEdge TrustLint

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 text must be non-empty content to evaluate (empty/whitespace is rejected before any rule runs; this is not a system-risk questionnaire). Optional jurisdiction is EU, US, or GLOBAL; omit it to evaluate the full corpus. GLOBAL is a separate corpus tag, not the union of EU and US : reuse the same token you used with list_rules for a scoped check. Runs fully offline : no network call, no API key, no credentials stored, no writes outside the process, read-only and idempotent; regex match against the bundled corpus; does not classify AI-system risk tiers or call any remote API. Returns PASS/FAIL with rule ID, severity, citation, and remediation.

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 jurisdiction is EU, US, or GLOBAL; omit it to list the full corpus. GLOBAL is a separate corpus tag, not EU∪US : pass that exact token into check_compliance next for a consistent scoped evaluation. Returned total is the post-filter count. Runs fully offline : no network call, no API key, no credentials stored, no writes outside the process, read-only and idempotent. Returns rule IDs, titles, severities, jurisdictions, and categories.

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 prompt must be a non-empty candidate prompt about to be sent to a model (empty/whitespace is rejected; not already-produced output). This tool has no jurisdiction filter : it always evaluates the full bundled corpus. Runs fully offline : no network call, no API key, no credentials stored, no writes outside the process, read-only and idempotent; regex match against the bundled corpus; does not classify AI-system risk tiers or call any remote API. Returns SAFE or RISK_DETECTED with cited findings from the offline regex corpus.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 3 tools

Disambiguation4/5

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.

Naming Consistency5/5

All three tools use a consistent snake_case verb_noun pattern: list_rules, check_compliance, scan_prompt. The convention is predictable and readable throughout.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivityActive
ResponsivenessUnresponsive