Skip to main content
Glama

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

Tools

Functions exposed to the LLM to take actions

NameDescription
get_dashboardB

Get current revenue dashboard with all key metrics

get_pipelineA

Get all leads in the pipeline

add_leadC

Add a new lead to the pipeline

update_leadC

Update an existing lead

search_gmailC

Search Gmail inbox

get_email_contentC

Get full content of an email thread

write_matrix_entryC

Write entry to Knowledge Matrix

query_matrixC

Search Knowledge Matrix

browse_pageB

Navigate to URL and return page content

take_screenshotC

Capture screenshot of webpage

save_browser_sessionD

Save browser session

read_fileB

Read file contents

write_fileD

Write file contents

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 13 tools

Disambiguation5/5

Each tool targets a distinct resource and action: dashboard metrics vs. pipeline leads, Gmail search vs. email content, knowledge matrix write vs. query, and browser vs. file operations. No two tools appear to perform the same function, and their descriptions make the boundaries clear.

Naming Consistency5/5

All tool names follow a consistent lower_snake_case verb_noun pattern, such as get_dashboard, add_lead, search_gmail, write_matrix_entry, and read_file. There are no mixed conventions, vague one-word names, or irregular verb styles.

Tool Count4/5

With 13 tools, the count is well within a reasonable range for a multi-purpose assistant spanning CRM, email, knowledge, browser, and file domains. The set is broad but each tool earns its place, though the wide scope keeps it from feeling tightly focused.

Completeness3/5

Core workflows are covered for each domain, but there are notable gaps: no send/reply for Gmail, no delete/list for files or leads, and limited browser interaction beyond navigation and screenshots. Agents can complete basic tasks but may hit dead ends in fuller lifecycle workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues