Skip to main content
Glama
meerkatsai

Lead Routing MCP Server

by meerkatsai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LEAD_ROUTING_DUCKDBNoPath to the DuckDB warehouse file. Default: warehouse/lead_routing.duckdb.warehouse/lead_routing.duckdb
LEAD_ROUTING_LEDGERNoPath to the SQLite workflow ledger file. Default: warehouse/ledger.sqlite.warehouse/ledger.sqlite
LEAD_ROUTING_FAKE_CRMNoPath to the fake CRM SQLite file. Default: warehouse/fake_crm.sqlite.warehouse/fake_crm.sqlite
LEAD_ROUTING_POLICY_VERSIONNoVersion identifier for the routing policy. Default: v1.v1
LEAD_ROUTING_ENTERPRISE_THRESHOLDNoEmployee-count threshold used by the enterprise routing rule. Default: 200.200

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_leads_for_routingB

List up to limit leads (max 100) with a one-line summary each. Read-only.

get_lead_contextB

Return the normalized lead plus account, open opportunities, territory and source timestamps. Read-only.

preview_routeB

Run the deterministic routing policy for one lead and return the decision. Does not write anywhere.

preview_route_with_country_hintA

Preview a route for a lead whose country is missing, using a country you inferred from its notes.

country_code must be a two-letter code; evidence must quote the text that supports it. The hint is validated, the normal policy runs on it, and the result is always marked for human review. Does not write anywhere.

get_routing_caseA

Return a workflow case (status, decision, attempts, errors, audit events) by case ID, or all cases for a lead ID.

explain_routing_policyA

Return the ordered routing rules, the policy version and the enterprise threshold.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation4/5

The two preview tools overlap in purpose, but the country-hint variant is clearly scoped to missing-country leads with validation and human review. The remaining tools target distinct read operations: cases, policy, lead lists, and lead context.

Naming Consistency5/5

All tool names use consistent snake_case with predictable verb-led phrasing such as preview_route, get_routing_case, explain_routing_policy, and list_leads_for_routing. The one longer variant, preview_route_with_country_hint, still follows the same convention.

Tool Count5/5

Six tools is well-scoped for a focused lead-routing server. Each tool supports a distinct part of the read/preview/explain workflow without excessive surface area.

Completeness3/5

The server covers previewing decisions, inspecting cases, explaining policy, listing leads, and fetching lead context. However, it lacks any write or execution operation for actually routing a lead or creating/updating workflow cases, which is a notable gap for a routing system.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources