Skip to main content
Glama

apex-dev

Url threat check

url_threat_check
Read-onlyIdempotent

Check any URL for phishing, brand impersonation, Punycode/IDN homographs, credential tricks, executable downloads, DNS resolution, and redirect chain risk (SAFE/CAUTION/RISKY). $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
urlYesFull http(s) URL to check for phishing and threat signals.
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: a per-call price ($0.001), accepted payment rails (x402/USDC on Arc, Base, Solana, XNT on X1), and the mandatory quote-then-pay handshake. It does not describe the shape of the verdict payload beyond the three labels, which keeps it below 5.

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?

Two dense sentences, front-loaded with the capability and verdict scale, then the commercial/payment mechanics. No filler. The signal list is long but each item is informative, so the density earns its place.

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?

With no output schema, the description carries the burden of explaining returns, and the SAFE/CAUTION/RISKY scale covers the essentials. The pricing and payment handshake — the highest-risk failure mode for an agent — are fully specified. Minor gap: no mention of latency, rate limits, or what accompanies each verdict level.

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 description coverage is 100%, so both `url` and `payment` are already documented in the schema. The description adds meaningful semantics for `payment` by framing the first call as a terms/quote request and the second as the paid call, but contributes nothing new about the `url` parameter. Baseline 3 fits.

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 and resource ('Check any URL') and enumerates exactly what signals are examined — phishing, brand impersonation, Punycode/IDN homographs, executable downloads, DNS, redirect chains — plus the three-level verdict scale. That specificity separates it from generic URL tools, though no sibling is named explicitly.

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 two-call payment flow is spelled out ('call once without `payment` for terms, then call again with `payment`'), which is genuine procedural guidance. However there is no guidance on when to choose this over url_status, link_check, or security_headers, and no stated 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