Skip to main content
Glama

How to block fake signups on a stack

how_to_block
Read-onlyIdempotent

Returns setup steps and links for blocking disposable and fake signups on a given stack: next.js, supabase, clerk, better-auth, auth.js, firebase, laravel, django, or html (any form: Webflow, Framer, WordPress).

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": {
      "stack": "<stack>"
    },
    "name": "how_to_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
stackYesThe framework or auth provider

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the return payload contains setup steps plus external links, which is genuinely useful context, but it does not say how the content is scoped, how long it is, or whether it varies by stack depth. A 3 is appropriate given annotations carry the safety burden.

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?

A single front-loaded sentence with the verb and result stated first, followed by the valid inputs. It is efficient, but the full re-listing of all nine enum values largely duplicates the schema and could have been shortened.

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?

For a one-parameter, no-output-schema guidance tool this is nearly complete: it says what comes back (steps and links) and what inputs are accepted. Only the absence of any statement about output shape or usage conditions keeps it from a 5.

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% and the enum is already documented, so the baseline is 3. The description earns above baseline by explaining the non-obvious 'html' value — '(any form: Webflow, Framer, WordPress)' — which tells the agent that no-code site builders should map to html rather than being unsupported, information the schema does not convey.

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 opens with a specific verb and resource ('Returns setup steps and links') and names the exact subject matter (blocking disposable and fake signups). An agent can immediately tell this is a guidance/how-to tool, clearly distinct from the validation siblings check_domains, check_email, and same_inbox, though it never states that contrast itself.

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 implied by the phrase 'on a given stack' and the enumerated stack list — call it when you need per-stack setup instructions. There is no explicit when-to-use/when-not guidance and no mention of the sibling tools or when a validation tool would be more appropriate instead.

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.

Resources