Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

check_url_advanced

check_url_advanced
Read-onlyIdempotent

Retrieve detailed URL intelligence—risk score, domain, DNS, content, and security signals—to assess safety and legitimacy before use.

Instructions

Retrieves advanced information about an url address (url, createdAt, updatedAt, state, requestedUrl, message, success, unsafe, domain, ipAddress, countryCode, languageCode, server, contentType, statusCode, pageSize, domainRank, dnsValid, parking, pageTitle, shortLinkRedirect, hostedContent, riskyTld, spfRecord, dmarcRecord, mxRecords, nsRecords, aRecords, errors, riskScore, suspicious, phishing, malware, spamming, adult, category, technologies, domainAge, redirected, scannedUrl, finalUrl) Args: url: valid url address

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

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety and repeatability are covered. The description's added value is the long enumeration of result fields (riskScore, phishing, malware, dnsValid, etc.), which hints at behavioral outcomes, but it says nothing about latency, rate limits, error handling, or whether the call is synchronous versus polled.

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 one-sentence purpose is front-loaded, but the enormous parenthetical field dump is unstructured and hard to scan, and its ordering (url, createdAt, updatedAt, ..., finalUrl) carries no grouping logic. It is justified only because no output schema exists.

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?

Given one required param and no output schema, the field list does compensate for the missing return-value contract, which is genuinely useful. But it omits the operationally important context an agent needs: whether results are immediate, how failures surface, and how this differs from sibling check tools.

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?

With a single parameter and 0% schema description coverage, the schema alone provides only "type: string". The description adds the constraint that the value must be a "valid url address", which is meaningful but minimal; it does not state accepted formats, scheme requirements, or whether bare domains are allowed.

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 ("Retrieves advanced information about an url address") and enumerates the returned fields, so the agent knows exactly what comes back. It does not, however, distinguish this from the other check_*_advanced siblings or explain what "advanced" adds over a basic check.

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as check_async_status or the non-advanced variants. The only guidance is the argument line "url: valid url address".

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.