rd-station-crm
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RD_STATION_TOKEN | Yes | Your RD Station CRM API token |
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 |
|---|---|
| rdstation_list_contactsC | List contacts from RD Station CRM. |
| rdstation_get_contactA | Get a single contact from RD Station CRM by id. |
| rdstation_create_contactA | Create a contact in RD Station CRM. |
| rdstation_update_contactC | Update fields of an existing contact in RD Station CRM. |
| rdstation_delete_contactB | Delete a contact from RD Station CRM by id. |
| rdstation_list_organizationsB | List organizations (companies) from RD Station CRM. |
| rdstation_get_organizationA | Get a single organization from RD Station CRM by id. |
| rdstation_list_dealsB | List deals (negócios) from RD Station CRM. |
| rdstation_get_dealB | Get a single deal from RD Station CRM by id. |
| rdstation_create_dealB | Create a deal in RD Station CRM. |
| rdstation_update_dealC | Update fields of an existing deal in RD Station CRM. |
| rdstation_win_dealB | Mark a deal as won in RD Station CRM. |
| rdstation_lose_dealC | Mark a deal as lost in RD Station CRM, optionally with a lost reason id and note. |
| rdstation_list_deal_pipelinesA | List deal pipelines (funis) configured in RD Station CRM. |
| rdstation_list_deal_stagesA | List the stages of a deal pipeline in RD Station CRM. Omit deal_pipeline_id to list all pipelines with their stages. |
| rdstation_list_usersA | List users (team members) from RD Station CRM. |
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 16 tools
Each tool targets a distinct resource-action pair: contact CRUD, organization read, deal management, pipeline/stage listing, and user listing. Actions like win_deal and lose_deal are clearly separate from generic update_deal, so there is no real ambiguity.
All tools share the rdstation_ prefix and follow a consistent snake_case verb_noun pattern (list_contacts, get_contact, update_deal, win_deal). The naming is predictable and makes the tool family easy to navigate.
At 16 tools, the set is at the upper edge of the ideal range but each tool maps to a meaningful CRM operation. The breakdown across contacts, deals, organizations, pipelines, and users is reasonable, though it is slightly heavy.
Contacts have full CRUD coverage and deals cover the main lifecycle including win/lose, but organizations are read-only with no create/update/delete. There is also no deal deletion, which leaves notable lifecycle gaps for the stated CRM domain.