Skip to main content
Glama

LeadShield Contact Form & B2B Solicitation Blocker

Screen a contact form message

leadshield_screen_submission
Read-onlyIdempotent

Check a message against the connected site's spam rules and, when configured, its intent classifier. Returns the screening decision and reason. This preview does not store the message, send it to a customer, or process a payment.

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>",
      "message": "<message>"
    },
    "name": "leadshield_screen_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSubmitter full name.
siteYesA site connected to your LeadShield account, such as 'review-demo'.
emailNoSubmitter email address.
phoneNoSubmitter phone number.
countryNoTwo-letter ISO 3166-1 alpha-2 country code (e.g. 'US', 'CA').
messageYesInbound form message or inquiry text to evaluate.
formTypeNoOptional form-type preset to evaluate against.
timezoneNoSubmitter IANA timezone (e.g. 'America/Los_Angeles').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / formType / enum
      Previous value: -[
      -  "general_inquiry",
      -  "quote_request",
      -  "booking_request",
      -  "b2b_partnership",
      -  "support_ticket",
      -  "careers_application",
      -  "warranty_claim",
      -  "event_registration",
      -  "newsletter_signup",
      -  "feedback_review"
      -]New 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 client or site slug (e.g. 'pacific-coast-detailing', 'moosh-works')."New value: +"A site connected to your LeadShield account, such as 'review-demo'."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds meaningful behavioral detail by clarifying that this preview does not store the message, send it to a customer, or process a payment. It also notes that the intent classifier is used only when configured, which adds useful context beyond the 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 three concise sentences that front-load the core screening action and immediately clarify the preview's side-effect profile. Every sentence contributes useful information without repetition or waste.

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?

With annotations covering safety profile and the schema covering all parameters, the description supplies the key missing context: that this is a preview, returns a decision and reason, and does not trigger downstream effects. A slightly fuller explanation of the return shape would be needed to reach the highest level given the absence of an output schema.

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 itself fully documents all eight parameters, including the site, message, and formType enum. The description mentions only the message and connected site at a high level and does not add parameter-specific syntax or constraints beyond the schema.

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 a specific verb and resource: checking a message against the connected site's spam rules and optional intent classifier, then returning a screening decision and reason. It is readily distinguishable from sibling tools that configure policies, generate embeds, or retrieve reports.

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 word "preview" and the explicit note that it does not store, send, or process payment make the intended non-production screening context clear. However, it does not explicitly name when to use this versus alternatives or state exclusions, so it falls short of full when/when-not guidance.

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.