Privacy Policy URL

Check A2P 10DLC documents before registering

check_a2p_10dlc_documents

Read-onlyIdempotent

Opens a business's privacy policy, SMS terms and opt-in page (public https links) and checks what US carrier reviewers look for before approving an A2P 10DLC texting campaign: the non-sharing statement and no wording that lets mobile data go to third parties (Twilio 30908, 30932), frequency, "Message and data rates may apply", STOP and HELP in the terms, and an opt-in that is never pre-ticked (30924). Returns verdict and pass/warn/fail checks per page. Pattern checks, not a carrier's decision; nothing is stored.

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": {
      "privacyUrl": "<privacyUrl>"
    },
    "name": "check_a2p_10dlc_documents"
  }
}

Input Schema

Name	Required	Description	Default
`optInUrl`	No
`termsUrl`	No
`privacyUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses that it fetches live public https pages, that nothing is stored, that it returns a verdict plus pass/warn/fail per page, and that results are heuristic rather than authoritative. That is meaningful added context for a network-reading tool. Not covered: behavior on unreachable or non-https URLs, and any latency/timeout expectations for opening three external pages.

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?

The purpose is front-loaded and the rule list is packed into one dense but readable sentence; the caveat clause at the end is short and load-bearing. The middle enumeration is long, but each listed rule is specific and earns its place rather than padding.

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 states the return shape (verdict, pass/warn/fail per page), and it covers the check semantics and side-effect profile needed to call it. The remaining omission is optionality of two of three parameters and error behavior for bad URLs.

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?

Schema description coverage is 0%, so the description must carry the load, and it does map the parameters to page roles (privacy policy, SMS terms, opt-in page) and adds a constraint absent from the schema: links must be public https. It does not reveal that only privacyUrl is mandatory while termsUrl and optInUrl are optional, nor what happens when an optional page is omitted.

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 (opens and checks) against specific resources (privacy policy, SMS terms, opt-in page) and names the concrete goal: US carrier review criteria for A2P 10DLC registration. It enumerates the exact rules checked (30908, 30932, 30924, STOP/HELP, non-sharing), so the tool's function is unambiguous. It stops short of naming the closest sibling, check_privacy_policy_url, so an agent must infer which of the two to reach for.

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 phrase 'before approving an A2P 10DLC texting campaign' gives a clear triggering context, and 'Pattern checks, not a carrier's decision' warns the agent not to present results as approval. There is no explicit when-not guidance and no mention of the overlapping check_privacy_policy_url sibling, which is the main gap.

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

All Privacy Policy URL tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?