Skip to main content
Glama

Numbers Online — phone intelligence

by online.numbers

Do-not-contact supplementary signal

dnc_check
Read-onlyIdempotent

Return a first-party do-not-contact signal (suppress / no_match / unknown) for a number, sourced ONLY from suppression preferences registered and verified by the number's own owner inside Numbers Online — never a copy of any government or licensed do-not-call registry. "suppress" = the owner asked not to be contacted on this channel; "no_match" = no suppression preference on record (absence of suppress is not consent); "unknown" = the number could not be evaluated. Comes with a signed receipt recording the status "as of T". Advisory input to the agent's own process — it does not assert that a call is lawful.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesPhone number in E.164, e.g. +14155552671 (loose input is normalized).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint, openWorldHint), description adds that the signal is sourced only from owner-registered preferences, never from government DNC registries, and comes with a signed receipt. No contradiction with annotations.

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?

Description is detailed but well-structured, explaining three outcomes, sourcing, and advisory nature. Slightly lengthy but efficient for the information conveyed.

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?

Given one parameter with full schema coverage, no output schema, and helpful annotations, the description fully covers the tool's purpose, return values, and limitations (not a legal assertion). Complete for its complexity.

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 100% for the single parameter 'number', which is well described in the schema (E.164 with normalization). The description adds no extra meaning for the parameter beyond what the schema provides.

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?

Description clearly states it returns a do-not-contact signal (suppress/no_match/unknown) for a number, sourced only from the number's owner preferences, distinguishing it from government registries and sibling tools like caller_risk or phone_lookup.

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?

Description implies it is an advisory input and not a legal assertion, but lacks explicit guidance on when to use versus alternatives or when not to use. No exclusions mentioned.

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

All Numbers Online — phone intelligence toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation3/5

Tools overlap significantly: phone_lookup includes spam signals and DNC check, while caller_risk and dnc_check provide more specific or constrained functionality. Descriptions help differentiate use cases, but an agent might struggle to choose between them.

Naming Consistency4/5

All tool names use snake_case and are descriptive (e.g., caller_risk, dnc_check, line_type, phone_lookup). The pattern is mostly consistent, though verbs and noun combinations vary slightly.

Tool Count5/5

Four tools cover the core needs of phone intelligence (quick classification, risk assessment, DNC check, comprehensive lookup) without redundancy. The scope is well-matched to the domain.

Completeness4/5

The set covers essential operations for phone intelligence: basic line info, risk, DNC, and a full lookup. Minor gaps exist (e.g., no tool for updating DNC preferences), but given the server's advisory role, these are acceptable.

Resources