Skip to main content
Glama

LexQ

by io.lexq.mcp
OverviewDiscussionsAdmin

Deploy to Live

lexq_deploy_live
Destructive

Deploy an ACTIVE (published) version to live traffic. Takes effect immediately. Versions whose effective start date has not arrived are rejected (P-037) — use lexq_deploy_schedule for those. Undefined facts do not block deployment (INV-4); use lexq_facts_unregistered to review what the version references but has not defined.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoYesDeployment memo (required)
groupIdYesPolicy group ID
versionIdYesVersion ID to deploy

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / groupId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • addedInput schema / properties / versionId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. Changed1 schema field changed
    • changedInput schema / properties / memo / description
      Previous value: -"Live Deployment memo (required)"New value: +"Deployment memo (required)"
  3. Changed4 schema fields changed
    • removedInput schema / properties / memo / default
      Removed value: -""
    • changedInput schema / properties / memo / description
      Previous value: -"Deployment memo"New value: +"Live Deployment memo (required)"
    • addedInput schema / properties / memo / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
-  "groupId",
-  "versionId"
-]New value: +[
+  "groupId",
+  "versionId",
+  "memo"
+]
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, so the mutation profile is known. The description adds concrete behavioral details: immediate effect, rejection of future-dated versions (P-037), and that undefined facts do not block deployment (INV-4). This goes beyond annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each carrying distinct value: the action, the immediate effect, and two edge-case conditions with sibling routing. No filler, front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema, the description covers all critical behavior: what is deployed, when it takes effect, what is rejected, and what does not block. An agent has everything needed to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter has a description. The tool description does not add semantic nuance to the parameters themselves (e.g., what constitutes a valid 'versionId' for deployment). Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise verb and resource — 'Deploy an ACTIVE (published) version to live traffic' — and immediately distinguishes it from lexq_deploy_schedule. The tool's role among the many lexq_deploy_* siblings is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when NOT to use this tool ('Versions whose effective start date has not arrived are rejected') and names the exact alternative (lexq_deploy_schedule). Also directs to lexq_facts_unregistered for reviewing undefined facts, providing clear routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LexQ toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources