Skip to main content
Glama

LeadShield Contact Form & B2B Solicitation Blocker

Generate a form guard setup snippet

leadshield_generate_guard_embed
Read-onlyIdempotent

Generate an HTML script snippet and setup addresses for a site. Choose HTML, HighLevel, WordPress, HubSpot, or Astro. The result is setup guidance; this tool does not install or activate the guard.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "leadshield_generate_guard_embed"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesYour site's LeadShield identifier, such as 'review-demo'.
formTypeNoOptional formType preset attribute.
platformNoTarget website or CRM platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / formType / enum
      Added value: +[
      +  "local_service",
      +  "b2b_saas",
      +  "b2b",
      +  "agency",
      +  "portfolio",
      +  "ecommerce",
      +  "booking",
      +  "quiz",
      +  "real_estate",
      +  "careers",
      +  "newsletter",
      +  "general",
      +  "general_inquiry",
      +  "quote_request",
      +  "booking_request",
      +  "b2b_partnership",
      +  "support_ticket",
      +  "careers_application",
      +  "warranty_claim",
      +  "event_registration",
      +  "newsletter_signup",
      +  "feedback_review"
      +]
    • changedInput schema / properties / site / description
      Previous value: -"Target site or client slug (e.g. 'pacific-coast-detailing')."New value: +"Your site's LeadShield identifier, such as 'review-demo'."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds real value by stating the output is guidance only and that no installation or activation happens — a boundary an agent could otherwise get wrong.

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

Conciseness4/5

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

Three short sentences with the artifact stated first and the scope limit last; nothing is padded. Minor looseness in the vague phrase 'setup addresses', which is never clarified.

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

Completeness4/5

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

No output schema exists, and the description does state the shape of the result ('setup guidance'), which is what an agent needs to know it will not get an applied configuration. It stops short of describing what the snippet or addresses contain, and omits the webhook config mentioned in the annotation title.

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 the schema documents `site`, `formType`, and `platform` fully. The description's platform list mirrors the enum but adds no syntax, defaults, or guidance on `site` or `formType` beyond what the schema already says.

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

Purpose4/5

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

States a specific verb and artifact: 'Generate an HTML script snippet and setup addresses for a site', plus enumerates the five target platforms. This clearly separates it from the sibling spam-policy/report/screen tools, though the annotation title's 'Webhook Config' output is never mentioned in the description.

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 selection guidance ('Choose HTML, HighLevel, WordPress, HubSpot, or Astro') and a clear negative boundary ('does not install or activate the guard'). No sibling alternatives are named, but the sibling set is unrelated enough that the when-not clause does the routing work.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.