Truecaller Data2 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authenticating with the Truecaller Data2 API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchC | Truecaller Search |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'search' has a distinct and clear purpose for searching Truecaller data, so agents cannot misselect between multiple options.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'search' follows a simple verb pattern, and there are no other tools to compare it against for inconsistency.
A single tool is too few for a server named 'Truecaller Data2 MCP Server', which suggests a broader data-related scope. This minimal set limits functionality and likely leaves significant gaps in handling Truecaller data operations, making it inappropriate for comprehensive use.
The tool set is severely incomplete for the implied domain of Truecaller data. With only a search tool, there are obvious gaps such as creating, updating, deleting, or retrieving specific data entries, which are essential for full CRUD/lifecycle coverage in a data server.