Skip to main content
Glama

LookupDock

scrub_phone

Scrub a US phone number for a calling list: line type, carrier, state Do Not Call, litigator and complainer listings, and a callable decision of yes, review or no with reasons. The result is data as supplied and does not clear a call. Credits: 10; The National Do Not Call Registry is not checked yet, so run your own federal scrub as well. Until the registry check is live no number comes back yes. A number whose only reason is federal_dnc_not_checked passed every check that ran, and still needs your own federal scrub. Until the scrub service is live this returns kind_not_available. Demo fixtures use none.

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": {
      "phone": "<phone>"
    },
    "name": "scrub_phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYes
countryNo
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Strong disclosure well beyond the annotations: it states the credit cost (10), that the federal DNC registry is not yet checked, that no number can return 'yes' until that check is live, that a lone federal_dnc_not_checked reason still requires the caller's own federal scrub, and that the service currently returns kind_not_available. It also clarifies the result 'does not clear a call' and that demo fixtures use none. It stops short of describing error modes or the response shape in detail.

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

Conciseness4/5

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

Front-loaded with the core action and return fields before caveats, which is the right ordering. There is some repetition around the federal DNC gap (the 'no number comes back yes' and 'only reason is federal_dnc_not_checked' sentences restate the earlier caveat), but each repetition adds a distinct operational nuance.

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 does the necessary work of enumerating return fields and the possible decision values, plus cost and current service limitations. What remains thin is the response envelope and idempotency behavior, minor relative to the coverage provided.

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 coverage is 0%, so the description carries the burden and only partially meets it: 'US phone number' usefully constrains scope and implies the country parameter is US-oriented. The idempotency_key parameter is never mentioned, nor is any format guidance for phone, leaving a meaningful gap for a 3-parameter tool.

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?

Names a specific verb ('scrub') and resource ('a US phone number for a calling list') and enumerates exactly what the result contains: line type, carrier, state DNC, litigator/complainer listings, and a yes/review/no callable decision. It does not explicitly contrast itself with the sibling check_phone, so an agent must infer the boundary from the 'calling list' framing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Contextual usage is implied by 'for a calling list' and the explicit instruction to 'run your own federal scrub as well', which is genuine usage guidance. However, there is no statement of when to prefer this over check_phone or when not to call it, and no prerequisites beyond the federal-scrub caveat.

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