Tracxn MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_companyB | Fetch detailed information about a company from Tracxn |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| tracxn_raw | Access raw JSON data from any Tracxn API endpoint (read-only) |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
The single tool follows a consistent verb_noun pattern (get_company), which is straightforward and predictable. Since there are no other tools, there is no inconsistency to evaluate.
A single tool is too few for a server named 'Tracxn MCP Server', which implies a broader scope related to company data. This minimal set feels thin and inadequate for typical agent workflows, limiting functionality to just fetching company details without supporting operations like search, update, or listing.
The tool surface is severely incomplete for a company data domain; it only provides a get operation for companies, with no support for searching, listing, creating, updating, or deleting data. This leaves significant gaps that will cause agent failures in handling common tasks.