Skip to main content
Glama

install_snippet

Idempotent

Insert a cookie-consent banner and legal-policy snippet into an HTML file before . Automatically matches your app's styles and avoids overwriting files without .

Instructions

Insert the LexVibe cookie-banner + hosted-policies snippet into an HTML file, right before . By default the banner is themed to match the app's own colors, fonts and radius (detected from its stylesheets). Idempotent: if the snippet is already in the file, nothing changes. If the file has no literal (e.g. a Next.js App Router layout.tsx), it does NOT modify the file: it returns the snippet plus exact instructions for you (the dev agent) to add it as JSX — it never corrupts user files. After deploying, confirm with verify_snippet that the snippet is live.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesPath of the file to install into (index.html, app/layout.tsx…).
langNoForce the banner's language as an ISO 639-1 code, e.g. 'en' or 'es' (one of the 12 LexVibe locales). Defaults to the page's own language.
appIdNoLexVibe app id, e.g. from claim_app/get_claim_status (defaults to the LEXVIBE_APP_ID env var; without either, the YOUR_APP_ID placeholder is used and flagged).
themeNoauto (default): match the banner to this app's colors, fonts and radius. off: LexVibe default look.
accentNoBanner accent color as a CSS hex value, e.g. #4f46e5. Defaults to the color detected from the app's own styles (see `theme`).
positionNoWhere the banner sits on screen: bottom (full-width bar), bottom-left or bottom-right (floating card in that corner). Defaults to bottom.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.1.11
    • changedInput schema / properties / lang / description
      Previous value: -"Force the banner language (default: the page's)."New value: +"Force the banner's language as an ISO 639-1 code, e.g. 'en' or 'es' (one of the 12 LexVibe locales). Defaults to the page's own language."
    • changedInput schema / properties / position / description
      Previous value: -"Where the banner sits on screen."New value: +"Where the banner sits on screen: bottom (full-width bar), bottom-left or bottom-right (floating card in that corner). Defaults to bottom."
  2. Changed3 schema fields changedv0.1.10
    • addedInput schema / properties / accent / description
      Added value: +"Banner accent color as a CSS hex value, e.g. #4f46e5. Defaults to the color detected from the app's own styles (see `theme`)."
    • changedInput schema / properties / appId / description
      Previous value: -"App id (defaults to LEXVIBE_APP_ID)."New value: +"LexVibe app id, e.g. from claim_app/get_claim_status (defaults to the LEXVIBE_APP_ID env var; without either, the YOUR_APP_ID placeholder is used and flagged)."
    • changedInput schema / properties / file / description
      Previous value: -"File to install into (index.html, app/layout.tsx…)."New value: +"Path of the file to install into (index.html, app/layout.tsx…)."
  3. First observedv0.1.9

TDQS

A4.5/5.0
Behavior5/5

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

The description significantly extends beyond annotations. It discloses idempotency, safe handling of non-HTML files (no corruption), behavior when </head> is missing (returns instructions instead of modifying), and the need for deployment verification. No contradictions with annotations.

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?

The description is concise (5-6 sentences) with a clear front-loaded main action. Every sentence adds essential information, with no wasted words.

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, the description fully explains tool behavior: what it does, idempotency, handling of edge cases (non-HTML files), and follow-up action (verify_snippet). Complete for its complexity.

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 description coverage is 100%, so baseline 3. The description adds minimal extra meaning beyond schema defaults (e.g., lang defaults to page language, appId from env). No substantial additional semantics.

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 clearly states the tool inserts a LexVibe cookie-banner and hosted-policies snippet into an HTML file before </head>. It distinguishes itself from sibling tools like verify_snippet, scan_project, etc., which have different purposes.

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?

The description implies usage context (installing snippet) and mentions post-installation verification with verify_snippet, but does not explicitly list when to use or not use this tool versus alternatives. Still clear enough.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/marcosnovo/lexvibe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server