Skip to main content
Glama
mambalabsdev

mcp-contact-classifier

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesYour Apify API token. Get it at https://console.apify.com/account/integrations

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
classify_contactA

One contact in, one classified row out. Give it a job title and it returns the department, the seniority level, a seniority_rank from 1 to 12 you can filter with a comparison, and classification_rule, the named rule that fired, so every decision is auditable. The classification is a deterministic rule table: it needs no API key, calls no model, and returns the same answer for the same title every time. Only job_title is required. full_name and company_domain are read only when verify_position is on, which checks whether the person is still listed on their employer's own website and adds roughly 3 seconds and 9 requests per contact. The optional LLM fallback for titles the rules cannot place runs on your own key, set as the LLM_API_KEY secret environment variable on your own copy of the actor, and only the title is ever sent, never the person's name. With no key set those titles come back null rather than failing the row. This actor does not discover people: the name and title come from you. Requires an APIFY_TOKEN and consumes Apify credits. Read only.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap. Every call is unambiguously directed to classify_contact, making misselection impossible.

Naming Consistency5/5

The single tool name 'classify_contact' follows a clear verb_noun pattern and is descriptive. Consistency is trivially maintained when there is only one tool.

Tool Count4/5

The server is narrowly scoped to contact classification, and one tool covers the entire purpose. While below the typical 3-15 range, the focused design justifies the count, though it feels slightly thin.

Completeness5/5

The tool fully covers the classification operation: input a title, output department, seniority, rank, and classification rule. Optional verification and LLM fallback are integrated. No critical gaps or dead ends exist for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues