lexq

Server Details

Rule engine with built-in simulation. 55 MCP tools for complete business rule lifecycle management.

Status: Healthy
Last Tested: 2026-04-02 08:30
Transport: Streamable HTTP
URL

See and control every tool call

Log every tool call with full inputs and outputs

Control which tools are enabled per connector

Manage credentials once, use from any MCP client

Monitor uptime and get alerted when servers go down

Available Tools

55 tools

lexq_ab_test_adjustInspect

Adjust traffic weights of a running A/B test.

ParametersJSON Schema

Name	Required	Description
`groupId`	Yes	Policy group ID
`controlWeight`	Yes	New control weight (%)
`challengerWeight`	Yes	New challenger weight (%)

lexq_ab_test_startInspect

Start an A/B test on a policy group. Requires a challenger version ID and traffic split percentages.

ParametersJSON Schema

Name	Required	Description
`groupId`	Yes	Policy group ID
`identityKey`	No	Fact key for sticky assignment (e.g. customer_id)
`controlWeight`	Yes	Control traffic weight (%)
`challengerWeight`	Yes	Challenger traffic weight (%)
`challengerVersionId`	Yes	Challenger version ID

lexq_ab_test_stopInspect

Stop a running A/B test. Specify which version to keep.

ParametersJSON Schema

Name	Required	Description	Default
`groupId`	Yes	Policy group ID
`winnerVersionId`	Yes	Version ID to keep as live

lexq_dataset_templateInspect

Generate a sample CSV or JSON template based on the required facts of a version. Use this to understand the expected data format before uploading a dataset.

ParametersJSON Schema

Name	Required	Description	Default
`format`	No	Template format	csv
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID

lexq_dataset_uploadInspect

Upload inline CSV or JSON content as a simulation dataset. The content is uploaded to S3 and a path is returned. Use this path in simulation start with dataset type UPLOADED.

CSV example: user_id,payment_amount user_001,150000 user_002,50000

JSON example: [{"user_id":"user_001","payment_amount":150000}, {"user_id":"user_002","payment_amount":50000}]

ParametersJSON Schema

Name	Required	Description	Default
`content`	Yes	CSV or JSON content as string
`filename`	No	Filename with extension (.csv or .json)	dataset.csv

lexq_deploy_detailInspect

Get detailed info about a specific deployment including snapshot hash and integrity check.

ParametersJSON Schema

Name	Required	Description	Default
`deploymentId`	Yes	Deployment ID

lexq_deploy_historyInspect

List deployment history across all groups.

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number
`size`	No	Page size
`type`	No	Filter by deployment type
`groupId`	No	Filter by group ID

lexq_deploy_liveInspect

Deploy an ACTIVE (published) version to live traffic. Takes effect immediately.

ParametersJSON Schema

Name	Required	Description
`memo`	No	Deployment memo
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID to deploy

lexq_deploy_overviewInspect

Show current deployment status of all groups — which version is live, last deployment type, and deployer.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

lexq_deploy_publishInspect

Publish a DRAFT version (DRAFT → ACTIVE). Locks the version from further edits. Must have at least one rule.

ParametersJSON Schema

Name	Required	Description
`memo`	No	Deployment memo
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID to publish

lexq_deploy_rollbackInspect

Rollback to the previous deployed version. Only available if there is a previous version.

ParametersJSON Schema

Name	Required	Description	Default
`memo`	No	Rollback reason
`groupId`	Yes	Policy group ID

lexq_deploy_undeployInspect

Remove the live version from traffic. The version stays ACTIVE but no longer serves requests.

ParametersJSON Schema

Name	Required	Description	Default
`memo`	No	Undeploy reason
`groupId`	Yes	Policy group ID

lexq_dry_runInspect

Execute a single dry run against a version. Tests how rules evaluate given input facts without side effects.

Example input: { "facts": { "payment_amount": 100000, "customer_tier": "VIP" } }

Always dry-run before publishing to validate rule behavior.

ParametersJSON Schema

Name	Required	Description
`facts`	Yes	JSON string of facts object, e.g. {"payment_amount":100000}
`versionId`	Yes	Policy version ID to test against
`includeDebugInfo`	No	Include execution and decision traces
`mockExternalCalls`	No	Mock external integration calls

lexq_dry_run_compareInspect

Compare dry run results between two versions using the same input facts. Useful for validating changes.

ParametersJSON Schema

Name	Required	Description
`facts`	Yes	JSON string of facts object
`versionIdA`	Yes	Baseline version ID
`versionIdB`	Yes	Candidate version ID

lexq_facts_createInspect

Register a new input variable. Key must be lowercase with underscores (e.g. payment_amount). Types: STRING, NUMBER, BOOLEAN, LIST_STRING, LIST_NUMBER.

ParametersJSON Schema

Name	Required	Description
`key`	Yes	Variable key (snake_case)
`name`	Yes	Display name
`type`	Yes	Value type
`isRequired`	No	Whether this fact is required for rule evaluation
`description`	No	Description

lexq_facts_deleteInspect

Delete a fact definition. System facts cannot be deleted.

ParametersJSON Schema

Name	Required	Description	Default
`factId`	Yes	Fact definition ID

lexq_facts_listInspect

List all fact definitions (input variable schema). Shows key, type, and required status. Always check this before creating rules.

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number
`size`	No	Page size
`keyword`	No	Search keyword

lexq_facts_updateInspect

Update a fact definition. Key and type cannot be changed. System facts only allow name and description changes.

ParametersJSON Schema

Name	Required	Description
`name`	Yes	Display name
`factId`	Yes	Fact definition ID
`isRequired`	Yes	Required flag
`description`	No	Description

lexq_groups_createInspect

Create a new policy group. Requires name and priority. Optionally set conflict resolution, activation group, and description.

ParametersJSON Schema

Name	Required	Description
`name`	Yes	Group name (unique among non-ARCHIVED)
`priority`	Yes	Execution priority (lower = higher)
`description`	No	Group description
`maxSelections`	No	Max selections (required when mode is MAX_N)
`activationGroupId`	No	Activation group ID
`conflictResolutionMode`	No	Conflict resolution mode
`conflictResolutionStrategy`	No	Strategy when mode is EXCLUSIVE or MAX_N

lexq_groups_deleteInspect

Archive a policy group. Only non-live groups can be deleted. This is irreversible.

ParametersJSON Schema

Name	Required	Description	Default
`groupId`	Yes	Policy group ID

lexq_groups_getInspect

Get a single policy group by ID.

ParametersJSON Schema

Name	Required	Description	Default
`groupId`	Yes	Policy group ID

lexq_groups_listInspect

List all policy groups. Supports pagination and optional status/keyword filters.

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number (0-indexed)
`size`	No	Page size
`status`	No	Filter by status
`keyword`	No	Search keyword

lexq_groups_updateInspect

Update an existing policy group. Only provided fields are updated.

ParametersJSON Schema

Name	Required	Description
`name`	No	New name
`status`	No	Status (DISABLED = emergency stop)
`groupId`	Yes	Policy group ID
`priority`	No	New priority
`description`	No	New description
`maxSelections`	No	Max selections
`conflictResolutionMode`	No	Conflict resolution mode
`conflictResolutionStrategy`	No	Strategy

lexq_history_getInspect

Get full execution detail including request facts, result traces, and decision traces.

ParametersJSON Schema

Name	Required	Description	Default
`executionId`	Yes	Execution history ID

lexq_history_listInspect

List policy execution history. Shows trace ID, group, version, status, match result, and latency.

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number
`size`	No	Page size
`status`	No	Filter by execution status
`endDate`	No	End date (yyyy-MM-dd)
`groupId`	No	Filter by policy group
`traceId`	No	Filter by trace ID
`startDate`	No	Start date (yyyy-MM-dd)
`versionId`	No	Filter by version

lexq_history_statsInspect

Get execution KPIs: total executions, success/failure counts, success rate, and average latency.

ParametersJSON Schema

Name	Required	Description
`endDate`	No	End date (yyyy-MM-dd)
`groupId`	No	Filter by policy group
`startDate`	No	Start date (yyyy-MM-dd)

lexq_integrations_config_specInspect

Show available integration types and their required configuration fields.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

lexq_integrations_deleteInspect

Delete an integration by ID.

ParametersJSON Schema

Name	Required	Description	Default
`integrationId`	Yes	Integration ID

lexq_integrations_getInspect

Get integration detail by ID.

ParametersJSON Schema

Name	Required	Description	Default
`integrationId`	Yes	Integration ID

lexq_integrations_listInspect

List all external integrations (webhooks, CRM, notification, etc.).

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number
`size`	No	Page size
`type`	No	Filter by integration type

lexq_integrations_saveInspect

Create or update an integration. Types: COUPON, POINT, NOTIFICATION, CRM, MESSENGER, WEBHOOK.

ParametersJSON Schema

Name	Required	Description
`name`	Yes	Integration name
`type`	Yes	Integration type
`apiKey`	No	API key or token for the service
`config`	No	JSON string of additional config key-value pairs
`baseUrl`	Yes	Base URL of the external service
`isActive`	No	Whether the integration is active

lexq_logs_actionInspect

Process a single failure log: RETRY, RESOLVE, or IGNORE.

ParametersJSON Schema

Name	Required	Description	Default
`logId`	Yes	Failure log ID
`action`	Yes	Action to take

lexq_logs_bulk_actionInspect

Process multiple failure logs at once. Provide an array of log IDs and the action.

ParametersJSON Schema

Name	Required	Description	Default
`action`	Yes	Action to apply to all logs
`logIds`	Yes	Array of failure log IDs

lexq_logs_getInspect

Get failure log detail by ID.

ParametersJSON Schema

Name	Required	Description	Default
`logId`	Yes	Failure log ID

lexq_logs_listInspect

List system failure logs from background tasks (webhook calls, coupon issuance, etc.).

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number
`size`	No	Page size
`status`	No	Log status
`endDate`	No	End date (yyyy-MM-dd)
`keyword`	No	Search in refId, refSubId, errorMessage
`category`	No	Task category
`taskType`	No	Task type
`startDate`	No	Start date (yyyy-MM-dd)

lexq_requirementsInspect

Analyze which input facts a version requires. Returns required keys, types, and an example request body.

ParametersJSON Schema

Name	Required	Description	Default
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID

lexq_rules_createInspect

Create a rule in a DRAFT version. Requires name, priority, condition tree, and actions array.

Condition: { type: "SINGLE", field, operator, value, valueType } or { type: "GROUP", operator: "AND"|"OR", children: [...] } Operators: EQUALS, NOT_EQUALS, GREATER_THAN, GREATER_THAN_OR_EQUAL, LESS_THAN, LESS_THAN_OR_EQUAL, CONTAINS, IN, NOT_IN Value types: STRING, NUMBER, BOOLEAN, LIST_STRING, LIST_NUMBER

Actions: [{ type, parameters }] Types: DISCOUNT, POINT, COUPON_ISSUE, BLOCK, NOTIFICATION, WEBHOOK, SET_FACT, ADD_TAG

ParametersJSON Schema

Name	Required	Description
`rule`	Yes	JSON string of CreateRuleRequest: { name, priority, condition, actions, mutexGroup?, mutexMode?, mutexStrategy?, mutexLimit?, isEnabled? }
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID

lexq_rules_deleteInspect

Delete a rule from a DRAFT version.

ParametersJSON Schema

Name	Required	Description
`force`	No	Skip confirmation (for the last rule in a version)
`ruleId`	Yes	Rule ID
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID

lexq_rules_getInspect

Get full rule detail including condition tree and action definitions.

ParametersJSON Schema

Name	Required	Description
`ruleId`	Yes	Rule ID
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID

lexq_rules_listInspect

List all rules in a version. Returns summary with conditionSummary and actionSummary.

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number
`size`	No	Page size
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID

lexq_rules_reorderInspect

Reorder rules by specifying rule IDs and their new priorities. Array index 0 = highest priority.

ParametersJSON Schema

Name	Required	Description
`groupId`	Yes	Policy group ID
`ruleIds`	Yes	Rule IDs in desired priority order
`versionId`	Yes	Version ID

lexq_rules_toggleInspect

Enable or disable a rule without deleting it.

ParametersJSON Schema

Name	Required	Description
`ruleId`	Yes	Rule ID
`groupId`	Yes	Policy group ID
`isEnabled`	Yes	true to enable, false to disable
`versionId`	Yes	Version ID

lexq_rules_updateInspect

Update an existing rule in a DRAFT version. Only provided fields are changed.

ParametersJSON Schema

Name	Required	Description
`rule`	Yes	JSON string of UpdateRuleRequest: { name?, priority?, condition?, actions?, mutexGroup?, mutexMode?, mutexStrategy?, mutexLimit?, isEnabled? }
`ruleId`	Yes	Rule ID
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID

lexq_simulation_cancelInspect

Cancel a running or pending simulation.

ParametersJSON Schema

Name	Required	Description	Default
`simulationId`	Yes	Simulation ID

lexq_simulation_exportInspect

Export simulation results as JSON or CSV. Returns the raw data.

ParametersJSON Schema

Name	Required	Description	Default
`format`	No	Export format	json
`simulationId`	Yes	Simulation ID

lexq_simulation_listInspect

List simulation history with optional filters.

ParametersJSON Schema

Name	Required	Description
`to`	No	End date (yyyy-MM-dd)
`from`	No	Start date (yyyy-MM-dd)
`page`	No	Page number
`size`	No	Page size
`status`	No	Filter by status

lexq_simulation_startInspect

Start a batch simulation against historical execution data.

Example body: { "policyVersionId": "", "dataset": { "type": "HISTORICAL", "source": "EXECUTION_LOGS", "from": "2025-01-01", "to": "2025-01-31" }, "options": { "baselinePolicyVersionId": "", "includeRuleStats": true, "maxRecords": 10000 } }

ParametersJSON Schema

Name	Required	Description	Default
`body`	Yes	JSON string of SimulationRequest

lexq_simulation_statusInspect

Get simulation status and results. Poll until status is COMPLETED or FAILED.

ParametersJSON Schema

Name	Required	Description	Default
`simulationId`	Yes	Simulation ID

lexq_versions_cloneInspect

Clone an existing version to create a new DRAFT. Useful when the source version is already published.

ParametersJSON Schema

Name	Required	Description
`groupId`	Yes	Policy group ID
`versionId`	Yes	Source version ID to clone
`commitMessage`	No	Commit message for the cloned version

lexq_versions_createInspect

Create a new DRAFT version in a policy group. Provide a commit message and optional effective date range.

ParametersJSON Schema

Name	Required	Description
`groupId`	Yes	Policy group ID
`effectiveTo`	No	Effective end date (ISO 8601)
`commitMessage`	Yes	Commit message describing this version
`effectiveFrom`	No	Effective start date (ISO 8601)

lexq_versions_deleteInspect

Delete a DRAFT version. Only DRAFT versions can be deleted.

ParametersJSON Schema

Name	Required	Description	Default
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID

lexq_versions_getInspect

Get a single version by ID, including its rules and fact requirements.

ParametersJSON Schema

Name	Required	Description	Default
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID

lexq_versions_listInspect

List all versions of a policy group.

ParametersJSON Schema

Name	Required	Description
`page`	No	Page number
`size`	No	Page size
`groupId`	Yes	Policy group ID

lexq_versions_updateInspect

Update a DRAFT version. Only DRAFT versions can be modified.

ParametersJSON Schema

Name	Required	Description
`groupId`	Yes	Policy group ID
`versionId`	Yes	Version ID
`effectiveTo`	No	New effective end date
`commitMessage`	No	New commit message
`effectiveFrom`	No	New effective start date

lexq_whoamiInspect

Show current authentication info (tenant name, role, API key mask).

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Verify Ownership

Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.

Server Details

Available Tools

Verify Ownership

Discussions

Your Connectors

Resources