Skip to main content
Glama

DropEngine x402 Agent Services

check_url

Paid Agent Preflight URL check ($0.005 USDC on Base). Call before an agent opens, follows, downloads from, or trusts an unknown URL. Performs deterministic checks, safely inspects HTTPS redirects without loading page content, blocks localhost/private addresses, and optionally queries Google Web Risk when configured. No LLM is used. A clean result is not a guarantee of safety.

Agent entry points: risky external action → use Agent Action Gate when a combined action-specific safety assessment is needed; unclear capability/provider → use free /api/discover; constrained comparison between callable alternatives → use paid route_tool; known single capability → call the direct tool; multi-step objective → read the matching workflow recipe and call only relevant steps. Workflows are stateless recipes, not executors; calls are paid separately and are not bundle charged. Agent Action Gate does not approve payment, sign or broadcast transactions, evaluate seller reputation, replace transaction simulation, replace route_tool, or replace human approval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNo
nextNo
safeYes
errorNo
httpsYes
cachedYes
resultNo
statusNo
malwareYes
paymentNo
sourcesYes
successYes
threatsYes
agent_uxNo
degradedYes
phishingYes
warningsYes
final_urlYes
checked_atYes
risk_levelYes
risk_scoreYes
normalized_urlYes
recommendationYes
redirect_countYes
domain_age_riskYes
recommended_nextNo
suspicious_domainYes
suspicious_redirectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / recommended_next / properties / recommendation_id
      Added value: +{
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
  2. Changed11 schema fields changed
    • addedOutput schema / properties / agent_ux
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "error": {
      +      "anyOf": [
      +        {},
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "meta": {
      +      "additionalProperties": {},
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "next": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "payment": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "execution_status": {
      +          "enum": [
      +            "not_started",
      +            "succeeded",
      +            "failed",
      +            "unknown"
      +          ],
      +          "type": "string"
      +        },
      +        "status": {
      +          "enum": [
      +            "not_required",
      +            "required",
      +            "settled",
      +            "failed",
      +            "unknown"
      +          ],
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "status",
      +        "execution_status"
      +      ],
      +      "type": "object"
      +    },
      +    "result": {},
      +    "status": {
      +      "enum": [
      +        "succeeded",
      +        "failed",
      +        "partial",
      +        "outcome_unknown"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "result",
      +    "error",
      +    "meta",
      +    "payment",
      +    "next"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / error
      Added value: +{
      +  "anyOf": [
      +    {},
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / meta
      Added value: +{
      +  "additionalProperties": {},
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / next
      Added value: +{
      +  "items": {},
      +  "type": "array"
      +}
    • addedOutput schema / properties / payment
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "execution_status": {
      +      "enum": [
      +        "not_started",
      +        "succeeded",
      +        "failed",
      +        "unknown"
      +      ],
      +      "type": "string"
      +    },
      +    "status": {
      +      "enum": [
      +        "not_required",
      +        "required",
      +        "settled",
      +        "failed",
      +        "unknown"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "execution_status"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / recommended_next / properties / availability
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / recommended_next / properties / availability_observation
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / recommended_next / properties / condition
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / recommended_next / properties / workflow_id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / result
      Added value: +{}
    • addedOutput schema / properties / status
      Added value: +{
      +  "enum": [
      +    "succeeded",
      +    "failed",
      +    "partial",
      +    "outcome_unknown"
      +  ],
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedOutput schema / properties / recommended_next
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "price": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "reason": {
      +      "type": "string"
      +    },
      +    "tool": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "tool",
      +    "reason",
      +    "price"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "cached": {
      +      "type": "boolean"
      +    },
      +    "checked_at": {
      +      "type": "string"
      +    },
      +    "degraded": {
      +      "type": "boolean"
      +    },
      +    "domain_age_risk": {
      +      "const": "unknown",
      +      "type": "string"
      +    },
      +    "final_url": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "https": {
      +      "type": "boolean"
      +    },
      +    "malware": {
      +      "type": "boolean"
      +    },
      +    "normalized_url": {
      +      "type": "string"
      +    },
      +    "phishing": {
      +      "type": "boolean"
      +    },
      +    "recommendation": {
      +      "enum": [
      +        "allow",
      +        "caution",
      +        "block"
      +      ],
      +      "type": "string"
      +    },
      +    "redirect_count": {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "risk_level": {
      +      "enum": [
      +        "low",
      +        "medium",
      +        "high",
      +        "critical"
      +      ],
      +      "type": "string"
      +    },
      +    "risk_score": {
      +      "maximum": 100,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "safe": {
      +      "type": "boolean"
      +    },
      +    "sources": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "success": {
      +      "const": true,
      +      "type": "boolean"
      +    },
      +    "suspicious_domain": {
      +      "type": "boolean"
      +    },
      +    "suspicious_redirect": {
      +      "type": "boolean"
      +    },
      +    "threats": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "warnings": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "safe",
      +    "risk_score",
      +    "risk_level",
      +    "recommendation",
      +    "normalized_url",
      +    "final_url",
      +    "redirect_count",
      +    "https",
      +    "domain_age_risk",
      +    "phishing",
      +    "malware",
      +    "suspicious_redirect",
      +    "suspicious_domain",
      +    "threats",
      +    "warnings",
      +    "sources",
      +    "cached",
      +    "degraded",
      +    "checked_at"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: discloses the $0.005 USDC cost, deterministic/no-LLM nature, that redirects are inspected without loading page content, that localhost/private addresses are blocked, optional Google Web Risk use, and an explicit limitation ('a clean result is not a guarantee of safety'). It stops short of error/timeout behavior or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and useful, but the trailing routing/disclaimer paragraph is long, generic, and reused boilerplate that dilutes the tool-specific payload. It earns partial place as sibling routing, but the ratio of boilerplate to signal is high.

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?

An output schema exists so return values need not be described, and the description covers trigger, cost, behavioral limits, and sibling routing. What remains thin is the input URL contract, which leaves a minor gap for a single required parameter.

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?

One parameter at 0% schema coverage, so the description must compensate. It gives context (an 'unknown URL' the agent may open/follow/download) but never states expected format, scheme requirements, or the 4096-character bound 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 and resource (URL preflight check) with cost and chain, and immediately scopes what it inspects. It is distinguishable from siblings like check_package and check_change by naming the target artifact (URL) explicitly.

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?

Explicit trigger ('Call before an agent opens, follows, downloads from, or trusts an unknown URL') plus a routing paragraph naming alternatives: Agent Action Gate for combined action safety, /api/discover for unknown capabilities, route_tool for comparisons. The routing block is largely generic boilerplate reused across siblings, which slightly weakens the tool-specific guidance.

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