Skip to main content
Glama

Web Reader & Search (Tanod)

check_url_phishing

Read-onlyIdempotent

chainpeek: Check if a URL or domain is phishing or a scam. For up to 1,000 URLs use check_urls_phishing_batch; for headers use check_security_headers. Returns whether a URL's host (or a domain) is on public phishing/scam domain lists: listed, the matched_domain, the sources that list it and shared_platform, with the lists' update time and a disclaimer. A screening aid: the host and its parent domains are matched against two public lists, PhishDestroy (CC0) and Phishing.Database (MIT), refreshed daily; the URL is never fetched. An unlisted host is not cleared: new phishing is on no list yet, and lists can be stale. Input that is not a URL, host or domain is a 422 invalid_input (not charged). Typically under 0.1 s (first call up to a few seconds). Price: USD 0.001. Free: 10 chain reads per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/phishing-scam-url-checker-api.html

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": "check_url_phishing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL, host or domain to screen (at most 2,048 characters); only parsed, never fetched.
domainNoAlternative to url: a domain or host name.

Output Schema

NameRequiredDescriptionDefault
hostNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
inputNo
listedNo
sourcesNo
disclaimerNo
matched_domainNo
list_updated_atNo
shared_platformNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / domain / default
      Removed value: -null
    • removedInput schema / properties / domain / title
      Removed value: -"Domain"
    • removedInput schema / properties / url / default
      Removed value: -null
    • removedInput schema / properties / url / title
      Removed value: -"Url"
    • removedInput schema / title
      Removed value: -"check_url_phishingArguments"
    • removedOutput schema / properties / sources / items
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "disclaimer": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "host": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "input": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "list_updated_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "listed": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "matched_domain": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "shared_platform": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "sources": {
      +      "items": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds materially: the URL is never fetched, submitted text is never logged or stored, input errors return 422 and are not charged, latency is typically under 0.1 s, and rate/pricing limits (10 free reads per IP per UTC day, USD 0.001). The one omission is that it doesn't say what the fields look like when no match occurs, though the output schema likely covers 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?

Purpose and sibling routing are front-loaded in the first sentence, followed by return shape, scope caveats, and operational facts. Nearly every clause carries information, though the vendor prefix, the doc URL, and the pricing/rate-limit details make it denser than strictly necessary for tool selection.

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

Completeness5/5

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

For a two-parameter read-only screening call, the definition covers the input contract, list sources and refresh cadence, the crucial false-negative caveat, error behavior, cost, and latency. With an output schema present it does not need to enumerate return fields further, and annotations already carry the safety semantics.

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%, so both `url` and `domain` are already documented, including that `domain` is an alternative to `url` and that the value is only parsed, never fetched. The description reinforces the URL-or-domain duality and adds one useful semantic rule — non-URL/host/domain input yields a 422 invalid_input rather than a result — but adds no format guidance beyond the schema. Baseline 3 is appropriate.

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?

Specific verb and resource: "Check if a URL or domain is phishing or a scam," immediately naming both accepted input forms. It explicitly distinguishes itself from check_urls_phishing_batch (bulk) and check_security_headers (headers), so the agent can route without opening sibling schemas.

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

Usage Guidelines5/5

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

Gives explicit alternatives and the conditions that select them: batch tool for up to 1,000 URLs, headers tool for header checks. It also states the limits of the answer ("an unlisted host is not cleared") so an agent knows when this result is insufficient rather than treating it as a clean verdict.

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.