Skip to main content
Glama

net_tools_cdn_fingerprint

[$x402 pago por llamada] Detecta CDN/WAF (Cloudflare, Akamai, CloudFront, Fastly, Vercel, Sucuri, Imperva, nginx/OpenResty, Varnish) a partir de headers HTTP (HEAD, con fallback a GET).

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": {
      "url": "<url>"
    },
    "name": "net_tools_cdn_fingerprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full load; it does add two useful behavioral facts: the x402 per-call payment requirement and the HEAD-with-GET-fallback probing method. It omits how failures/permission denials behave and whether the operation is purely read-only, leaving meaningful gaps for an unannotated tool.

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 payment tag first and the detection target immediately after; no filler. Slightly dense with the provider list, but every element is informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the definition should say what a result looks like (e.g., which CDN name is returned, confidence, or a null when nothing matches); it stays silent. Payment mechanics are delegated to the schema parameter description, so the core gap is return-value shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: x_payment is documented in the schema but url has no description, and the description never clarifies the expected URL format (scheme, host-only, path). The HEAD/GET mention describes internal behavior rather than the parameter, so it does not compensate for the gap.

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?

States a specific verb (detect) and resource (CDN/WAF) and enumerates the providers it can identify, so the intent is unambiguous. It does not, however, distinguish itself from near neighbors like net_tools_headers_audit or web_tools_tech_detect, which also inspect HTTP responses.

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

Usage Guidelines2/5

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

The description says what it detects but gives no guidance on when to reach for it versus headers_audit or tech_detect, nor any prerequisites beyond the payment note. Usage is only implied by the detection verb.

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