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.
1
MIT
eyecon
by com.jojapi
Server Details
Eyecon: Use the no.1 API for a true caller ID to identify name and see photos. 100% success rate.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.6/5.0
Tool DescriptionsA
Average 3.6/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
The two tools are completely distinct: one retrieves country codes, the other performs a search. There is no overlap or ambiguity between them.
Naming Consistency4/5
Both tools share the 'get_api_v1_' prefix, but the action parts are inconsistent: 'getCountryCode' is a noun phrase with camelCase, while 'search' is a bare verb. The shared prefix provides a consistent pattern, with minor deviation.
Tool Count3/5
At only 2 tools, the surface is quite thin, but it may be appropriate for a very narrow phone lookup service. It hovers on the border of feeling minimal for a full-featured server.
Completeness4/5
The tools cover the core workflow of fetching country codes and searching for contacts. Minor gaps exist such as lack of pagination or detail endpoints, but the primary use case is fully supported.
Available Tools
2 toolsget_api_v1_getCountryCodeGet Country CodeAInspect
Get list of all country codes. Billing per call: 1 Credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Definition Quality
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds a billing cost ('Billing per call: 1 Credits') and specifies the output (all country codes), but it doesn't explicitly state read-only semantics, authorization needs, or response format. The cost disclosure adds some transparency, but the overall behavioral picture is incomplete.
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 consists of two short sentences, front-loaded with the main purpose and immediately followed by cost information. Every sentence earns its place with no redundancy or filler.
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 the tool's simplicity (0 parameters, no output schema, no annotations), the description provides the essential context: it returns all country codes and costs 1 credit. It doesn't mention usage guidance or output format, but the core invocation context is sufficient for a 0-param reference data tool.
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 input schema has zero parameters and additionalProperties set to false, so there are no parameter details to document. With zero parameters, the baseline is 4, and the description correctly avoids adding irrelevant parameter semantics. The schema already fully covers the parameter space.
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 a specific verb-resource pair: 'Get list of all country codes.' It specifies the full scope ('all') and is distinct from the sibling get_api_v1_search, which likely performs searches rather than returning a reference list.
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?
The description provides no guidance on when to use this tool versus the sibling get_api_v1_search. It doesn't mention alternative use cases, exclusion criteria, or prerequisites, leaving the agent without context for tool selection.
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 ContactBInspect
Search for the contact based on phone number and country code. Billing per call: 1 Credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | ||
| number | Yes |
Tool Definition Quality
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits. It mentions billing (1 credit per call) but does not indicate side effects, permissions, response format, or any other operational nuances. For a search operation, it likely is read-only, but this is not stated.
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?
Description is short and front-loaded with the core purpose, followed by billing note. No redundant information; every sentence adds value.
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?
Tool is simple (2 params, no output schema, no annotations). The description covers the primary purpose and cost, but lacks information about response structure, error handling, or any prerequisites. It is adequate for basic use but not comprehensive.
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 description coverage is 0%, so the description must clarify parameters. It explicitly links 'phone number' to the 'number' parameter and 'country code' to 'code', providing basic semantics. However, it lacks format, length, or examples, which would be more helpful. Given the low coverage, this is a minimal but acceptable explanation.
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 searches for a contact using a phone number and country code, with specific resources and parameters. It differentiates from the sibling tool get_api_v1_getCountryCode, which likely retrieves country codes rather than searching contacts.
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 on when to use this tool versus alternatives. The sibling tool exists, but the description does not mention when one should be preferred over the other. No exclusions or contexts provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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 Servers
- Alicense-qualityBmaintenanceIdentity resolution MCP server for phone/email lookups across 31+ services. Provide detailed Identity info, Breach Info, Global + India coverage.1MIT
- Alicense-qualityDmaintenanceBest people search engine that reduces the time spent on talent discovery8MIT
- Alicense-qualityBmaintenanceFind professional email addresses from name + company domain. Tests 15+ patterns against MX records with confidence scoring, with pay-per-call via x402.MIT
