Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SF_PASSWORDYesSalesforce password
SF_USERNAMEYesSalesforce username
SF_LOGIN_URLYesSalesforce login URL (https://login.salesforce.com for production, https://test.salesforce.com for sandbox)
SF_SECURITY_TOKENYesSalesforce security token
SLACK_WEBHOOK_URLNoSlack webhook URL for notifications (optional)

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

Tools

Functions exposed to the LLM to take actions

NameDescription
check_order_statusB

Check an order's shipping status, carrier, tracking number, and ETA

create_returnC

Create a return order for a single line item in an order using standard Salesforce objects

email_return_labelC

Email the customer a PDF return label for an approved return order

update_case_statusC

Update a case status with optional priority and assignment changes

create_case_from_returnC

Create a case from an existing return order for tracking and follow-up

send_slack_alertC

Send a Slack alert notification

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. Tools like check_order_status, create_return, and email_return_label each target specific, non-overlapping actions in the order and return workflow, while send_slack_alert and update_case_status serve separate notification and case management functions.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern throughout (e.g., check_order_status, create_return, update_case_status), with only minor deviations such as send_slack_alert using 'send' instead of a more domain-specific verb, but overall it remains highly readable and predictable.

Tool Count5/5

With 6 tools, the server is well-scoped for its purpose of managing orders, returns, and cases. Each tool earns its place by covering distinct aspects of the workflow, from status checks to case creation and notifications, without feeling bloated or insufficient.

Completeness4/5

The tool set provides strong coverage for order and return workflows, including status checks, return creation, case management, and notifications. Minor gaps exist, such as no direct tool for creating or updating orders themselves, but agents can likely work around this using existing tools like create_return and update_case_status.

Maintenance

ActivityInactive
ResponsivenessNo issues