Skip to main content
Glama
Sign In

lexvibe

by io.github.marcosnovo
OverviewDiscussionsAdmin

Claim a real LexVibe app

claim_app

Create a REAL LexVibe app in the user's account (replaces any YOUR_APP_ID placeholder). Returns a claim link: show it to the user so they can sign in and confirm — the link stays valid for 7 days, so the user can open it later. On confirmation LexVibe creates the app, scans the URL (if given), generates and hosts the legal documents. After the user confirms, call get_claim_status with the returned code to retrieve the real app id and install snippet. Provide at least url or appName.

Input Schema

NameRequiredDescriptionDefault
urlNoPublic URL of the app: a website URL, or an App Store / Google Play listing URL for a mobile-only product. LexVibe scans whichever kind is provided on confirmation. If you don't have a listing URL yet, set `platform` explicitly instead.
aiActNoIf you already ran check_ai_act for this product, pass the SAME answers object here. The EU AI Act classification is then saved against the app on confirmation and shown in the user's dashboard, instead of being lost when this conversation ends.
answersNoCompliance flags you already know (pass check_website's suggestedAnswers): usesAnalytics, processesPayments, usesGenerativeAI, collectsEmails, sharesWithThirdParties, platformType, companyEntity, contactEmail…
appNameNoApp / business name (required if no url is provided).
marketsNoRegions where the app has users; each market pack cites its own frameworks: eu → GDPR/ePrivacy, uk → UK GDPR/PECR, us → CCPA/CPRA, ca → PIPEDA, latam → LGPD…; 'global' is NOT a union of the others — it only cites generic OECD international privacy best practices, for users outside every listed market. To cover several specific frameworks, list each market explicitly, e.g. ['eu', 'us', 'latam']. Defaults to [eu].
platformNoTarget platform when there is no url to infer it from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / aiAct
      Added value: +{
+  "additionalProperties": {
+    "anyOf": [
+      {
+        "type": "boolean"
+      },
+      {
+        "items": {
+          "maxLength": 60,
+          "type": "string"
+        },
+        "maxItems": 8,
+        "type": "array"
+      }
+    ]
+  },
+  "description": "If you already ran check_ai_act for this product, pass the SAME answers object here. The EU AI Act classification is then saved against the app on confirmation and shown in the user's dashboard, instead of being lost when this conversation ends.",
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Public URL of the app (website or App Store / Google Play listing). LexVibe scans it on confirmation."New value: +"Public URL of the app: a website URL, or an App Store / Google Play listing URL for a mobile-only product. LexVibe scans whichever kind is provided on confirmation. If you don't have a listing URL yet, set `platform` explicitly instead."
  3. Changed1 schema field changed
    • changedInput schema / properties / markets / description
      Previous value: -"Regions where the app has users. Defaults to [eu]."New value: +"Regions where the app has users; each market pack cites its own frameworks: eu → GDPR/ePrivacy, uk → UK GDPR/PECR, us → CCPA/CPRA, ca → PIPEDA, latam → LGPD…; 'global' is NOT a union of the others — it only cites generic OECD international privacy best practices, for users outside every listed market. To cover several specific frameworks, list each market explicitly, e.g. ['eu', 'us', 'latam']. Defaults to [eu]."
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare it is a non-read-only, non-destructive, closed-world mutation. The description goes well beyond that, disclosing the async two-step confirmation model, that a claim link is returned and valid for 7 days, that the app is only created on user confirmation, and that URL scanning plus legal-document generation/hosting happen as side effects.

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?

Front-loads the core action, then presents the return value and the next step in workflow order. Every clause — link validity, confirmation trigger, side effects, follow-up call — carries actionable information, with no filler.

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?

Despite no output schema, nested objects, and six parameters, the description covers the return artifact (claim link), its lifetime, the confirmation flow, the deferred side effects, and the follow-up tool call. Nothing needed to invoke and correctly sequence this tool is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds a genuine cross-parameter constraint absent from the schema: at least one of url or appName must be supplied despite zero required parameters. It does not elaborate on markets, platform, or aiAct beyond what the schema already documents.

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?

States a specific verb and resource ('Create a REAL LexVibe app in the user's account') with clear scope, and the parenthetical about replacing the YOUR_APP_ID placeholder removes ambiguity about which app is affected. The follow-up tool get_claim_status is named, so an agent can place this in the workflow without opening the schema.

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

Usage Guidelines4/5

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

Gives explicit sequencing guidance: show the link, wait for user confirmation, then call get_claim_status with the returned code. Also states the minimum input requirement ('Provide at least url or appName'). It lacks an explicit when-not-to-use note relative to upstream tools like check_website, but the operating context is clear.

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

All lexvibe 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