Skip to main content
Glama
scamverifyai

ScamVerify

check_phone

Read-onlyIdempotent

Verify US phone numbers for scam reports, robocall flags, carrier information, and community alerts. Get risk scores and detailed threat intelligence from FTC, FCC, and carrier data sources.

Instructions

Look up a US phone number to check for scam reports, carrier info, network status, robocall flags, and community reports. Returns a risk score (0-100), verdict, and detailed signals from FTC, FCC, carrier, and community data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phone_numberYesUS phone number to look up (any format: +1XXXXXXXXXX, (XXX) XXX-XXXX, etc.)
force_refreshNoForce a fresh lookup, bypassing cache (default: false)

Implementation Reference

  • The 'check_phone' tool is defined using server.tool. It takes phone_number and force_refresh as inputs, calls the '/api/v1/phone/lookup' endpoint, and handles success/error responses.
    server.tool(
      'check_phone',
      'Look up a US phone number to check for scam reports, carrier info, network status, robocall flags, and community reports. Returns a risk score (0-100), verdict, and detailed signals from FTC, FCC, carrier, and community data.',
      {
        phone_number: z.string().describe('US phone number to look up (any format: +1XXXXXXXXXX, (XXX) XXX-XXXX, etc.)'),
        force_refresh: z.boolean().optional().describe('Force a fresh lookup, bypassing cache (default: false)'),
      },
      {
        title: 'Check Phone Number',
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: true,
      },
      async ({ phone_number, force_refresh }) => {
        try {
          const data = await apiPost('/api/v1/phone/lookup', { phone_number, force_refresh });
          return jsonResult(data);
        } catch (err) {
          return errorResult(err instanceof Error ? err.message : 'Phone lookup failed');
        }
      },
    );
Behavior4/5

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

Annotations cover safety profile (readOnly, idempotent, destructive), so the description adds value by detailing return values (risk score 0-100, verdict, signals) and data sources (FTC, FCC, carrier, community) that would otherwise be unknown without an 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?

Two sentences with zero waste: first establishes purpose and checked attributes, second details return values. Every word earns its place and critical information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Excellent completeness given no output schema exists: the description fully compensates by detailing the risk score range, verdict structure, and data sources. Combined with comprehensive annotations and 100% param coverage, the agent has sufficient information to invoke and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, baseline is 3. The description adds contextual meaning by reinforcing the geographic scope ('US phone number') and connecting the parameter to specific use cases (scam detection, carrier lookup), providing semantic context beyond the schema's format instructions.

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?

The description uses specific verbs ('Look up') and clearly identifies the resource ('US phone number') and scope ('scam reports, carrier info, network status, robocall flags'). The singular phrasing implicitly distinguishes it from the sibling batch_phone tool.

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?

The description establishes clear context by specifying 'US phone number,' implying geographic limitation. However, it does not explicitly contrast with batch_phone for bulk operations or clarify when to use other check_* siblings versus this one.

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