Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Identify crawlers and Googlebot IPs

web-technology_crawler-identify
Read-onlyIdempotent

Match crawler-user-agents patterns and optionally verify Googlebot IPs against vendored Googlebot CIDR ranges. Price $0.02 USDC. POST /api/v1/web-technology/crawler-identify. An unpaid call returns the x402 payment terms and does not run.

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": {
      "userAgent": "<userAgent>"
    },
    "name": "web-technology_crawler-identify"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNoip, string. Optional.
userAgentYesuserAgent, string, length 1 to 2000. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
operatorNooperator. String.
isCrawlerNoisCrawler. Boolean.
ipVerifiedNoipVerified. Boolean.
limitationsNolimitations. Array.
matchedPatternNomatchedPattern. String.
spoofSuspectedNospoofSuspected. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior, so the description only needs to add payment context — which it does well: $0.02 USDC, the POST endpoint, and the critical detail that an unpaid call returns x402 payment terms without executing. It does not explain what the paid response contains, but an output schema exists for that.

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?

Front-loaded with the core capability, then the commercial and transport facts in short sentences with no filler. The raw endpoint path is the least valuable sentence for an agent but is a single clause and typical for API-backed tools.

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?

Covers purpose, cost, payment gating, and the conditional IP check, and the annotations plus output schema relieve it of safety and return-value duties. The one gap is what happens when `ip` is supplied for a non-Googlebot user agent — whether it is ignored or still evaluated.

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 a baseline of 3 applies, but the description earns an extra point by giving real meaning to the bare `ip` parameter: it is used specifically to verify Googlebot claims against Google's CIDR ranges, not for arbitrary IP lookups. That scope constraint is not present in 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?

States a specific verb+resource pair: matching crawler user-agent patterns, with an optional Googlebot IP check against vendored CIDR ranges. The function is clearly distinct from the sibling user-agent-parse tool, which parses rather than classifies crawlers.

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?

The word 'optionally' before the IP verification is the only usage signal, and it helps an agent decide whether to pass `ip`. There is no explicit guidance on when to prefer this over web-technology_user-agent-parse, nor any stated preconditions or exclusions.

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