Skip to main content
Glama

Sprawdź numer telefonu (PL)

check_phone_number
Read-onlyIdempotent

Check the reputation of a Polish phone number to identify spam, scams, or spoofed calls. Provides operator info, risk label, and verification against official registries.

Instructions

Sprawdź reputację polskiego numeru telefonu. UŻYJ, gdy użytkownik pyta: kto dzwonił, czy numer to spam/oszustwo, czy telefon rzekomo z banku lub urzędu jest prawdziwy. Zwraca operatora z zakresów UKE (z notą o przenośności MNP), etykietę ryzyka z opinii, status w wykazie DNO UKE (połączenie przychodzące z numeru DNO jest sfałszowane — spoofing), wpis z Białej Listy oficjalnych infolinii i liczniki zgłoszeń. Dane: numertel.pl.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesPolski numer w formacie 9 cyfr, np. 510100100 (akceptowane +48 i spacje — zostaną usunięte)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
e164Yes
is_dnoYes
numberYes
dno_noteNo
operatorNo
score_avgNo
whitelistNo
spam_labelYes
attributionYes
number_typeNo
operator_noteNo
sightings_30dNo
total_opinionsYes
Behavior4/5

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

Annotations (readOnlyHint=true, idempotentHint=true) are complemented by description adding details on DNO UKE spoofing check and data source numertel.pl. No contradictions.

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 concise and front-loaded with use cases, but could be structured with bullets for clarity; still efficient.

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 1 parameter and output schema existence, description covers key return fields and tool purpose adequately.

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 coverage is 100%; description adds format cleaning (spaces and +48 accepted and removed) beyond schema's basic format note.

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 the tool checks reputation of Polish phone numbers, listing specific outputs (operator, risk label, DNO status, White List entry, counters) and distinguishing from siblings like check_scam_domain.

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?

Explicitly tells when to use: when user asks about who called, spam/scam, authenticity of bank/official calls. Does not explicitly exclude other cases, but guidance is strong.

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/AMR-DEV-PS/numertel-mcp'

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