Potarix enricher

Official

by Potarix

Overview Schema Source Related Servers Score Discussions Admin

TypeScript

Hybrid

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.2
Disambiguation5/5
Each tool has a clearly distinct purpose: check_balance for account info, individual email lookup tools for different sources, a composite find_all, website lookup, and billing management. No overlap or ambiguity.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case (e.g., check_balance, find_company_emails, topup_credits). No mixing of conventions or irregular names.
Tool Count5/5
9 tools are well-scoped for a company/email enrichment service with account and billing features. Each tool serves a necessary function without superfluous additions.
Completeness4/5
The tool surface covers main workflows: account info, various email lookups, website resolution, and billing. A minor gap is the lack of a tool to list or manage API keys, but the core functionality is solid.
Average 4.1/5 across 9 of 9 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
This repository includes a glama.json configuration file.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive, but the description adds a critical non-obvious behavior: it consumes Potarix Enricher API credits. This cost side effect is not captured by annotations and is essential for an agent to know before invocation. It does not mention rate limits or return shape, but the annotation coverage reduces the need for those details.
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 exactly two sentences: the first states the purpose, and the second states the cost implication. It is front-loaded, actionable, and contains zero filler words.
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 tool with only one string parameter, complete schema coverage, and strong annotations, the description is adequately complete. It specifies the input domain, the purpose, and the credit cost. The lack of explicit return format or sibling differentiation is a minor gap, but the low complexity and available annotations make this sufficiently informative for correct use.
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?
The schema already provides 100% description coverage for the single `domain` parameter, including an example ('stripe.com'). The tool description merely restates 'for a domain' and adds no additional meaning beyond what the schema provides, so the baseline score of 3 applies.
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 uses a specific verb and resource: 'Find public company email contacts for a domain.' This clearly distinguishes it from sibling tools like find_person_email and find_decision_maker_email, which target individual contacts rather than general company 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?
The description does not provide any guidance on when to use this tool versus the sibling alternatives. It does not mention that find_person_email is for individual people or that find_decision_maker_email is for leadership contacts, leaving the agent to infer the scope from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the tool uses Potarix Enricher API credits, a cost-related behavior not captured by the annotations (readOnly, openWorld, idempotent, destructive). It adds this useful context without contradicting any annotations, though it does not mention what happens when no email is found.
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 two sentences with no wasted words. The first sentence states the exact purpose, and the second provides a critical cost warning. It is front-loaded and highly scannable.
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 read-only tool with comprehensive annotations and schema descriptions, the description adequately conveys core functionality and cost. However, it does not specify return values or edge cases (e.g., no email found), and the absence of an output schema makes this gap more noticeable.
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?
The schema describes all 5 parameters with full coverage (100%), so the description adds no parameter-specific meaning. The mention of 'named person at a company or domain' generally aligns with the parameters but does not enrich them beyond the schema descriptions.
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 finds a verified email for a named person at a company or domain, using a specific verb and resource. This distinguishes it from sibling tools like find_company_emails and find_decision_maker_email, which target company-wide or role-specific emails respectively.
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 you should use this tool when you have a person's full name and a domain or company, but it does not explicitly state when to use it over alternatives or provide exclusions. No sibling tool is named for comparison, so usage guidance remains implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnly/idempotent/openWorld signals, and the description adds valuable context about API credit consumption (Potarix Enricher API credits) and the verification aspect. It doesn't cover edge cases like not-found results, but the added cost details go beyond the annotations.
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 extremely concise, with two sentences that front-load the core purpose and then mention the API credit usage. No redundancy or wasted words.
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 two-parameter tool with strong annotations and no output schema, the description adequately explains the key behavior and cost. It could specify the exact return format, but the essential information—what is found and at what cost—is present.
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?
The input schema already provides thorough descriptions for both parameters—domain ('stripe.com') and category ('ceo', 'sales', 'operations')—so the description adds no extra parameter-specific meaning. With 100% schema coverage, the baseline score of 3 is appropriate.
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: to find a likely decision maker and verified email for a domain. This distinguishes it from sibling tools like find_person_email (specific person) and find_company_emails (company email list).
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 intended usage is implied by the name and description (search by domain and decision maker category), but there is no explicit guidance on when to choose this over alternatives like find_person_email or find_company_emails.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds a behavioral consequence not covered by annotations — that using it consumes Potarix Enricher API credits — and implies 'best' selection logic.
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?
Two short sentences immediately convey purpose and a key caveat (API credits). No wasted words or redundant repetition.
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 simple lookup with good annotations and full schema coverage, the description is adequate. It omits return type and error handling, but the purpose and credit cost are clear enough for basic use.
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?
The input schema covers 100% of parameters with descriptions, so the description adds no extra meaning about parameter usage. It does not go beyond what the schema already provides.
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 states a specific action ('Find') and a specific resource ('the best website URL') for a given company name, clearly differentiating it from sibling tools that target emails or account operations.
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?
The description provides clear context for when to use this tool (when you need a company's website URL) and even mentions credit usage, but it does not explicitly list alternatives or when-not-to-use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explains the interaction flow: the human must click the URL, and after completion, subsequent `topup_credits` calls are off-session. It also warns the agent not to follow the URL itself. This adds valuable behavioral context beyond the annotations, which only specify read-only and idempotency flags without detail.
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 three short sentences, starting with the primary function, then the consequence, then a usage directive. No unnecessary words; every sentence adds value.
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 single-parameter tool with no output schema and clear annotations, the description covers the essential aspects: return value, required human action, and subsequent effect on `topup_credits`. It also provides a direct usage instruction. Minor gaps like failure behavior or idempotency are not addressed but are not critical for this tool's simplicity.
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?
The input schema already provides full coverage for the single `tier_key` parameter, including allowed values and a description. The tool description itself does not add new semantic details about the parameter, though the title clarifies it's for the initial checkout. Since schema coverage is 100%, the baseline score of 3 applies.
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 Stripe Checkout URL for one-time card capture, distinguishing it from the sibling `topup_credits` tool. The verb 'Return' and resource 'Stripe Checkout URL' are specific. The follow-up behavior for `topup_credits` further clarifies its role.
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?
It implies when to use: before `topup_credits`, and explicitly states future `topup_credits` calls become off-session charges. It also gives a clear directive to hand the URL to the user and not follow it. However, it does not explicitly name alternatives or state when not to use this tool, though the sibling context makes it clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable behavioral context beyond annotations by disclosing that the tool uses Potarix Enricher API credits, implying a cost per call. This is a meaningful additional trait not covered by the annotations.
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 concise sentence that front-loads the core purpose and adds the important credit usage note without any wasted words. Every element earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one well-documented parameter and strong annotations, the description is complete. It explains what the tool does, what input it expects, and a key constraint (credit usage). No output schema is needed since the purpose ('find a verified email') implies the return value.
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?
The input schema already provides a clear description for the only parameter (linkedin_url) with 100% coverage, so the schema carries the full semantic weight. The tool description merely repeats 'LinkedIn profile URL' without adding extra meaning, so a baseline score of 3 is appropriate.
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: find a verified email from a LinkedIn profile URL. This specific verb+resource combination distinguishes it from sibling tools like find_company_emails or find_person_email, which target different input types or sources.
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?
The description provides clear context for when to use the tool: when you have a LinkedIn profile URL and need a verified email. It also adds a cost-related guideline by mentioning the use of Potarix Enricher API credits, though it does not explicitly exclude alternatives or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds value by disclosing cost behavior (sum of sub-calls, Potarix credits) and the composite nature of the call, which goes beyond the annotations. It does not contradict annotations.
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?
Three sentences pack crucial information: the composite scope, pricing implications, and API credit source. No fluff, each sentence earns its place. The informal 'kitchen-sink' opener is efficient and memorable.
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 complex composite tool with no output schema, the description does a good job: it enumerates the three sub-results, mentions cost considerations, and points to docs. It does not detail return format or error behavior, but given the annotations and the explicit doc reference, the description is sufficiently complete for agent selection.
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%, so the baseline is 3. The description adds meaning by connecting 'pricing is the sum of underlying sub-calls' to skip_company_emails (as a way to save credits) and by indicating dm_categories maps to the 'categories you request.' These additions provide semantic value beyond the schema's existing property descriptions.
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 composite action: resolving a website, finding decision-maker emails, and pulling the company-wide email roster all in one call. It effectively distinguishes itself from sibling tools like find_company_emails or lookup_company_website by framing it as a combined 'kitchen-sink' option.
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?
The description implies usage when multiple lookups are needed at once and mentions cost trade-offs ('Pricing is the sum of underlying sub-calls'), but it does not explicitly state when NOT to use it or directly compare to alternatives. The context is clear enough that an agent can infer when it fits, but explicit exclusions are missing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive hints. The description adds meaningful behavioral context beyond those: 'Free — does not consume credits' clarifies billing impact, and 'calling key's' specifies scope. No contradictions with annotations.
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?
Two concise sentences: first lists the exact output fields, second states the free behavior. Every word is meaningful, and the most important action ('Show the calling key's profile') is front-loaded. No fluff or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite lacking an output schema, the description explicitly enumerates all returned fields, so the agent knows exactly what to expect. Given the simplicity (no params, read-only, free), the description fully covers behavioral and return-value information without excess.
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 schema coverage is trivially 100%. The baseline for 0 params is 4, and there is nothing to clarify. The description correctly omits parameter details, keeping focus on the return data.
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 states a specific verb ('Show') and resource ('calling key's profile') with detailed output fields (email, credits, total purchased, card on file, active API keys). This is clearly distinct from sibling tools that search emails or handle checkout/topup.
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?
The context is unambiguous: this tool shows account/balance info for the calling key. No alternative sibling tool serves this purpose, so exclusions are unnecessary. The description implies when to use it by enumerating the exact data returned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds context beyond destructiveHint=true: it charges off-session and returns immediately on success. However, it does not mention failure scenarios (e.g., insufficient funds).
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?
Two succinct sentences with no extraneous information. Key points (buying, charging, alternative) are front-loaded and clearly separated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter tool with annotations already indicating destructive nature, the description covers the core workflow, prerequisites, and behavior. No output schema is needed, and the description suffices.
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?
The input schema already covers the parameter tier_key with enum values and descriptions. The description adds no further parameter information beyond what the schema provides (100% coverage).
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 begins with 'Buy a credit pack', clearly specifying the verb 'buy' and the resource 'credit pack'. It distinguishes from sibling tools by referencing start_checkout as a prerequisite when no card is saved.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit guidance on when to use this tool (buying credits) and when to use an alternative (start_checkout if no card is saved), including exact tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Potarix enricher MCP server – quality and maintenance score on Glama

Copy to your README.md:

[![Potarix enricher MCP server – quality and maintenance score on Glama](https://glama.ai/mcp/servers/Potarix/potarix-mcp/badges/card.svg)](https://glama.ai/mcp/servers/Potarix/potarix-mcp)

Score Badge

Copy to your README.md:

[![Potarix enricher MCP server – quality and maintenance score on Glama](https://glama.ai/mcp/servers/Potarix/potarix-mcp/badges/score.svg)](https://glama.ai/mcp/servers/Potarix/potarix-mcp)