Skip to main content
Glama

agent-exec

Check a URL against public risk feeds (paid, x402)

check_url

PAID: check a URL against public risk feeds (phishing lists, domain age, lexical signals): verdict, score, reasons. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: $0.0100 USDC.

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

Input Schema

NameRequiredDescriptionDefault
urlNoAn http(s) URL or bare domain, at most 2048 UTF-8 bytes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, openWorldHint=false and destructiveHint=false, so extra credit goes to the description for disclosing that the tool is paid ($0.0100 USDC), the exact payment envelope key, and the supported chains — genuinely useful context the annotations do not carry. However, it omits what an unpaid or underpaid call returns beyond 'the price', whether failed payments are charged, and any rate limits or caching window (the 'Read daily; no individual reply' line about feedback is too terse to be clarifying).

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

Conciseness5/5

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

Front-loads 'PAID:' so the cost is the first thing an agent sees, then covers what is checked, the payment loop, and feedback in compact sentences with no filler. The chain list is long but each token is decision-relevant for payment.

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 correctly names the return fields (verdict, score, reasons) and explains the payment handshake end to end, which is what an agent needs to invoke a single-parameter paid endpoint. It is only slightly short on failure modes — what happens on repeated unpaid calls or unsupported chains.

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?

Only one parameter and schema description coverage is 100%, so the schema already defines the URL as an http(s) URL or bare domain up to 2048 bytes. The description adds no format, normalization, or edge-case guidance (e.g., redirects, IDN, private hosts) beyond what the schema states, so baseline 3 applies.

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 a URL against public risk feeds') and enumerates the evidence sources (phishing lists, domain age, lexical signals) plus the return shape (verdict, score, reasons). It distinguishes itself from check_address/check_counterparty by naming URL-specific signals, though it never explicitly contrasts with those siblings.

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?

Gives an explicit call sequence: first call unpaid to learn the price, pay via x402 into _meta['x402/payment'], then call again. That is clear operational context with the accepted chains and asset (USDC on Base, Solana, Polygon, etc.) spelled out. It lacks when-not guidance (e.g., when to prefer check_address) but the paid flow is unambiguous.

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.