Skip to main content
Glama
WGalyean50

Salesloft MCP Demo Server

by WGalyean50
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_callsA

List available call transcripts with optional filtering.

Args:
    company: Filter by company name (partial match, case-insensitive)
    deal_stage: Filter by deal stage (Discovery, Demo, Negotiation, etc.)
    limit: Maximum results to return (default: 50, max: 100)

Returns:
    JSON array of call summaries with metadata
get_callA

Get the full transcript content for a specific call.

Args:
    call_id: The unique identifier for the call

Returns:
    Full transcript content including metadata and transcript text
search_callsA

Search for keywords across all call transcripts.

Args:
    query: Search terms (case-insensitive, searches all transcript content)
    limit: Maximum excerpts to return (default: 10, max: 50)

Returns:
    JSON array of matching excerpts with call context

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
list_all_transcriptsGet a complete list of all available call transcripts. Returns: JSON array of all call metadata
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 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity: get_call retrieves a specific transcript, list_calls provides filtered summaries, and search_calls finds keywords across content. The descriptions reinforce these distinct roles, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (get_call, list_calls, search_calls) with snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.

Tool Count3/5

With only 3 tools, the server feels thin for a Salesloft domain that likely involves more operations like creating or updating calls. While the tools cover core retrieval and search, the count is borderline for a comprehensive CRM or sales tool integration.

Completeness2/5

The tool surface is significantly incomplete for a Salesloft demo server, lacking essential CRUD operations such as creating, updating, or deleting calls. There are also gaps in related functionalities like managing deals or contacts, which agents might expect in this domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources