A
licenseC
qualityD
maintenanceEnables phone number lookup through the Truecaller Data2 API, allowing users to search and retrieve information about phone numbers for identification and verification purposes.
6
1
MIT
viewcaller
by com.jojapi
Server Details
ViewCaller: Find any phone number, have more information about your contacts & much more. Phone.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
2 toolsget_api_v1_getCountryCodeGet Country CodeAInspect
Returns a list of all countries supported by the ViewCaller API, including country name, dialing code, ISO codes, population, area, and GDP information. Billing per call: 1 Credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description adds useful behavior details: it notes billing per call (1 Credit) and scopes results to 'all countries supported by the ViewCaller API.' However, it does not explicitly state read-only nature or lack of side effects, though 'returns' implies a read operation.
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?
The description is a single sentence that efficiently conveys the output, scope, and billing. No filler or redundant text.
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?
For a parameter-less list retrieval, the description covers the key output fields and billing. It could mention potential pagination or ordering, but given the simplicity and lack of output schema, it is sufficiently complete.
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?
The tool has zero parameters, so the description does not need to explain parameter syntax. The baseline of 4 applies because there is no parameter information to add beyond the empty schema.
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 clearly states the tool returns a list of all countries supported by the ViewCaller API with specific fields (name, dialing code, ISO codes, etc.). It uses a specific verb 'returns' and identifies the resource, making it distinct from the sibling search tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus the sibling get_api_v1_search. The description only explains what it does, leaving the agent to infer use cases without explicit direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_api_v1_searchSearch ContactAInspect
Searches for contact information and identifies the name associated with a given phone number Billing per call: 1 Credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | ||
| number | Yes |
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It adds a billing note ('Billing per call: 1 Credits'), which is useful context beyond the basic action. However, it does not disclose potential errors, limitations, or data source specifics, leaving some behavioral gaps.
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 description is a single sentence and relatively concise, combining purpose and billing info. However, it lacks proper punctuation (missing period before 'Billing') and mixes two ideas without clear separation, slightly reducing clarity but not significantly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with no output schema, the description covers the main purpose and even mentions the output (associated name). However, it omits the meaning of 'code' and provides no usage context or edge-case behavior, leaving the tool somewhat incomplete for an agent to fully rely on.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has zero description coverage for the two parameters. The description explains that 'number' is a phone number, but it leaves 'code' completely undefined. This is a significant gap, as the agent cannot infer what 'code' represents, leading to potential misuse.
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 clearly states the tool's function: searching for contact information and identifying the name associated with a phone number. It uses a specific verb ('Searches') and resource ('contact information'), and distinguishes itself from the sibling tool (getCountryCode) by focusing on phone number to name 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?
The description implies usage: use when you need to identify a name from a phone number. However, it does not explicitly state when to use this tool versus the sibling getCountryCode, nor does it provide exclusions or alternative scenarios. Thus, only implied guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- First observed
get_api_v1_getCountryCode - First observed
get_api_v1_search
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Eyecon: Use the no.1 API for a true caller ID to identify name and see photos. 100% success rate.
NameResolver: The ViewCaller API empowers developers with powerful phone number intelligence and.
- mcpOAuthcom.skipshit
People and property search for Claude and ChatGPT. Phones, emails, addresses, relatives, properties.
Polish phone number lookup: who called, spam and scam checks, UKE DNO registry, CERT phishing stats
Related MCP Servers
- AlicenseAqualityCmaintenancePolish phone number lookup: who called, spam and scam checks, UKE DNO registry, CERT phishing stats51MIT
- AlicenseAqualityBmaintenanceProvides North American (NANP) area code and phone number intelligence for AI agents, including area code lookup, phone validation, carrier info, city/state coverage, local time, and scam context.858MIT
- AlicenseNot gradedqualityCmaintenanceValidates phone numbers and provides country calling codes, enabling AI agents to look up international dialing codes and filter by country name, ISO code, or calling code.18MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.6/5.0
Disambiguation5/5
The two tools have clearly distinct purposes: one retrieves a static list of country metadata, the other performs a phone number lookup. There is no overlap or ambiguity between them.
Naming Consistency3/5
Both tools follow a similar pattern with 'get_api_v1_' prefix, but the second part is inconsistent: 'getCountryCode' uses camelCase while 'search' is a bare verb. The prefix suggests an API endpoint structure rather than a consistent verb_noun convention.
Tool Count3/5
With only two tools, the server feels thin for a service that likely offers more functionality (e.g., reverse phone lookup, carrier info, validation). However, for a minimal API wrapper, two tools could be acceptable, so it's borderline.
Completeness2/5
The domain appears to be phone number lookup and country data, but the surface is severely limited. Missing obvious operations like phone number validation, detailed lookup results, or carrier information. The country list tool is a static reference, and the search tool is the only functional operation, leaving significant gaps.