momentic

check_bots

Probes a URL with multiple AI bot user-agents in parallel and returns per-bot reachability (status, key WAF/CDN headers, and a verdict). Reveals WAF/CDN-layer blocks that robots.txt audits miss — e.g. a site that allows GPTBot in robots.txt but returns 403 to it at Cloudflare. Verdicts: reachable, blocked-403, challenged-by-cdn, rate-limited-429, server-error-5xx, redirected-to-block-page, timeout, fetch-error. The summary.blockingPattern field names exactly which bots got blocked when others got through.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Absolute http(s) URL to probe
`timeoutMs`	No	Per-fetch timeout in ms (default 5000)
`userAgents`	No	Optional UA strings to test. Defaults to GPTBot, ClaudeBot, Claude-Web, PerplexityBot, GoogleOther, Google-Extended, CCBot, Applebot-Extended, ChatGPT-User, meta-externalagent.

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description fully discloses parallel probing, per-bot status, verdicts, and the blockingPattern field. It covers key behavioral aspects beyond the basic action.

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 a single, well-structured paragraph with no wasted words. Every sentence adds value, and the information is front-loaded.

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?

Given the absence of an output schema, the description adequately explains the return format (per-bot status, verdict, blockingPattern). It covers the essential outcomes for a tool of this complexity.

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 coverage is 100%, and the description adds minimal extra meaning (default values). The baseline of 3 is appropriate as the schema carries most parameter documentation.

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 the tool probes a URL with multiple AI bot user-agents and returns per-bot reachability, distinguishing itself from robots.txt audits by revealing WAF/CDN-layer blocks.

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 description explicitly contrasts with robots.txt audits, indicating when to use this tool. It does not provide a full list of exclusions or alternatives, but the context is clear.

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

All momentic tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: page SEO vs site AI discovery vs bot checks vs graph computation vs link extraction vs brand info vs page fetching vs listing vs entity lookup vs freshness parsing vs search. No overlapping responsibilities.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in lower_snake_case (e.g., analyze_page, check_bots, compute_link_graph). No mixing of conventions.

Tool Count5/5

11 tools is well-scoped for the server's purpose (SEO/web analysis). Each tool earns its place, covering page, site, bot, link graph, entity, and freshness analysis without unnecessary bulk.

Completeness5/5

The tool surface appears complete for its domain: it covers individual page SEO, site-wide AI discovery, bot accessibility, link graph analysis, entity lookup, and freshness signals. No obvious gaps for the intended analysis workflows.

Resources

Need Help?