Skip to main content
Glama

LeadShield Contact Form & B2B Solicitation Blocker

Get Blocked Contact Form Spam Report & Metrics

leadshield_get_blocked_spam_report
Read-onlyIdempotent

Read blocked-message counts, categories, screening stages, and recent submissions for your connected sites. The date window uses UTC calendar days and includes today.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "leadshield_get_blocked_spam_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window in days (1 to 90, default 7).
limitNoMaximum number of recent blocked records to include (1 to 50, default 10).
clientSlugNoA connected site to report on. Omit to combine only the sites connected to your account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / clientSlug / description
      Previous value: -"Optional client slug filter (e.g. 'pacific-coast-detailing'). Omit for aggregate overview."New value: +"A connected site to report on. Omit to combine only the sites connected to your account."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds real context beyond that: the date window is defined in UTC calendar days and includes today, which directly affects how an agent interprets counts. Return shape and defaults are not restated, but the missing pieces are minor.

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 what is returned, followed by the one non-obvious semantic (UTC day window including today). Nothing is wasted and there is no repetition of schema content.

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 no output schema, the description carries the burden of indicating what comes back, and it does: counts, categories, screening stages, and recent submissions. Combined with complete parameter documentation and safe-read annotations, an agent has enough to call it correctly; only missing an explicit note on combined-sites defaults.

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%, with ranges, defaults, and the clientSlug omission behavior fully documented, so a baseline 3 applies. The description only adds the phrase 'for your connected sites', which slightly reinforces clientSlug scoping but adds no new syntax or semantics.

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?

The description names a specific verb-and-resource pair ('Read blocked-message counts, categories, screening stages, and recent submissions') and scopes it to connected sites. This clearly separates it from the policy-configuration and screening siblings, though it does not name them explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the description establishes that this is the reporting/read path versus configuring spam policy or screening a single submission. It never states when to prefer it over those siblings or any prerequisites (e.g. a connected site must exist).

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.