bd-crm-analytics
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT_ID | Yes | The UUID of the BD Leads project. | |
| CRM_BASE_URL | Yes | The base URL of the CRM (no trailing slash). | |
| CRM_API_TOKEN | Yes | Personal Access Token for the CRM API. | |
| WORKSPACE_SLUG | Yes | The workspace slug from the CRM URL. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_win_rateA | Win rate for the BD Leads pipeline. dimension='bd' gives overall + per-BD-rep win rates; dimension in profile|lead_source|country|contract_type gives win rate sliced by that field (leads, wins, closed and win % per value). |
| get_conversion_funnelB | Stage-conversion funnel (Applied → … → Won) with per-step conversion %, drop-off, and the biggest-leak stage. Snapshot of current pipeline positions. |
| get_connects_economicsA | Upwork connects economics: overall connects-per-win, connects ROI by segment (spend, connects/win, estimated revenue-per-connect, wasted connects) and a boosted-vs-not comparison. |
| get_velocity_and_cycleA | Sales velocity ($/day) with its four inputs (open opps, avg deal value, win rate, avg cycle length), plus average cycle length (created → Won) broken down by Profile and by Country. |
| get_forecastA | Weighted pipeline forecast: total estimated value of open leads, each weighted by its stage's win probability, with a per-stage breakdown. Deal value is an estimate. |
| list_leadsA | List BD leads (read-only, paginated) with key fields + BD custom fields. Filter by state (name or group), profile, country, and date range. Use list_metadata for valid values. |
| list_metadataA | List available custom fields (with their options) and pipeline states — the valid values for filtering (profiles, countries, contract types, states). Call this first to discover filters. |
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 7 tools
Each tool has a clearly distinct purpose: economics metrics, conversion funnel, forecast, velocity/cycle, win rate, leads listing, and metadata discovery. No overlap in functionality.
All tools follow a consistent verb_noun pattern using 'get_' for metrics and 'list_' for data retrieval. The naming is uniform and predictable.
Seven tools is appropriate for a CRM analytics server, covering key analytic dimensions without being overwhelming or too sparse.
The tool set covers the primary analytics needs: economics, funnel, forecast, velocity, win rates, plus leads listing and metadata. No obvious gaps for the intended purpose.