Skip to main content
Glama
scamverifyai

ScamVerify

batch_url

Read-onlyIdempotent

Analyze multiple URLs simultaneously for security threats by checking against 10M+ intelligence records from FTC, FCC, URLhaus, and other sources. Process up to 100 URLs in one request to identify risk scores and potential scams.

Instructions

Check multiple URLs in a single request (max 100). Each URL is analyzed individually with the same checks as check_url. Returns results array with per-item risk scores and a summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesArray of URLs to check (1-100)
force_refreshNoForce fresh lookups, bypassing cache (default: false)

Implementation Reference

  • Definition and implementation of the 'batch_url' tool. It takes an array of URLs and performs a batch lookup via the API.
    // 8. batch_url
    server.tool(
      'batch_url',
      'Check multiple URLs in a single request (max 100). Each URL is analyzed individually with the same checks as check_url. Returns results array with per-item risk scores and a summary.',
      {
        urls: z.array(z.string()).min(1).max(100).describe('Array of URLs to check (1-100)'),
        force_refresh: z.boolean().optional().describe('Force fresh lookups, bypassing cache (default: false)'),
      },
      {
        title: 'Batch URL Lookup',
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: true,
      },
      async ({ urls, force_refresh }) => {
        try {
          const data = await apiPost('/api/v1/batch/url', { urls, force_refresh });
          return jsonResult(data);
        } catch (err) {
          return errorResult(err instanceof Error ? err.message : 'Batch URL lookup failed');
        }
      },
    );
Behavior4/5

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

Annotations cover safety profile (readOnly, idempotent, non-destructive); description adds valuable behavioral context about return format ('results array with per-item risk scores and a summary') and implicitly references caching behavior via 'force_refresh' parameter, compensating for missing output schema.

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?

Three efficient sentences with zero waste: opens with action and limits, clarifies sibling relationship, and describes return structure. Every clause conveys essential information.

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?

Given the simple 2-parameter input schema and strong annotations, the description adequately compensates for the missing output schema by describing the risk scores and summary structure, though it could clarify the risk score scale or summary contents.

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 has 100% description coverage for both parameters (urls array constraints and force_refresh cache behavior), so the description appropriately does not redundantly explain parameters, meeting the baseline for high-coverage schemas.

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?

Explicitly states 'Check multiple URLs' with specific scope limit (max 100), and clearly differentiates from sibling tool 'check_url' by stating it uses the 'same checks'—making the batch vs. single relationship unambiguous.

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?

Implies when to use versus check_url (multiple URLs) and states the 100-item limit, but lacks explicit 'when not to use' guidance or mention of alternatives for non-URL content (e.g., check_document for files).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scamverifyai/scamverify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server