Skip to main content
Glama

LeadShield Contact Form & B2B Solicitation Blocker

Inspect Site Contact Form Spam Policy & Form-Type Presets

leadshield_get_spam_policy
Read-onlyIdempotent

Inspect the saved spam rules for a connected site, including countries, phone formats, URLs, keywords, and its form preset. Supply a formType to preview that preset without changing the saved policy.

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_get_spam_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesA site connected to your LeadShield account.
formTypeNoOptional formType preset to preview.

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 site or client slug (e.g. 'pacific-coast-detailing')."New value: +"A site connected to your LeadShield account."
  2. 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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful context about what is inspected (countries, phone formats, URLs, keywords, preset) and confirms that formType preview does not mutate the saved policy.

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?

Two sentences, front-loaded with the main action and scope, followed by the formType preview behavior. No unnecessary repetition or 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?

For a simple read-only inspection tool with full schema coverage and safety annotations, this is complete. The description lists the rule categories returned and clarifies the optional preview behavior.

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. The description adds meaning beyond the schema by explaining that formType previews a preset without altering the saved policy, which is not evident from the schema alone.

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: inspect saved spam rules for a connected site. It distinguishes itself from leadshield_configure_spam_policy by emphasizing that it reads the saved policy and previews presets without changing them.

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?

Clearly indicates when to use this tool: to inspect saved spam rules or preview a formType preset. It implicitly contrasts with the configuration sibling by saying the saved policy is not changed, though it does not explicitly name leadshield_configure_spam_policy as the alternative.

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.