Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COSMOS_KEYNoAzure Cosmos DB key
PALLAS_PORTNoPort for HTTP transport8080
PALLAS_KB_PATHNoPath to directory containing kb.json./data
COSMOS_DATABASENoCosmos DB database namepallas-kb
COSMOS_ENDPOINTNoAzure Cosmos DB endpoint (enables learning loop)
PALLAS_LOG_LEVELNoLog level: error, warn, info, debugerror
PALLAS_TRANSPORTNoTransport: stdio (local) or http (Azure)stdio

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
athena_search_kbA

Search the Athena Tools knowledge base. Returns views, columns, API endpoints, workflows, FHIR resources, gotchas, and error patterns relevant to the query. Every result includes a confidence score and the source tier (primary = verified live data, secondary = scraped docs, reference = public repos).

athena_explain_viewA

Returns detailed information about an athenahealth Snowflake DataView view: description, columns with data types, known enum values, FK relationships, and any operational gotchas. Use this before writing SQL against any view.

athena_explain_joinA

Explains how to join two athenahealth Snowflake DataView views. Returns the join columns, confidence level, known warnings (e.g. CONTEXTID requirements, multi-tenant row-level security), and a sample SQL snippet. Always call this before writing a JOIN to avoid silent data loss from incorrect key usage.

athena_diagnose_errorA

Diagnoses an athenahealth API or Snowflake DataView error. Returns likely causes, suggested fixes, and links to relevant knowledge base content. Handles HTTP status codes, athenahealth-specific error strings, OAuth/scope errors, and SQL errors.

athena_explain_workflowA

Explains a named athenahealth clinical or administrative workflow: the intended sequence of steps inside athenaOne, the API calls that correspond to each step, the Snowflake views that capture the workflow state, and common integration mistakes. Use this to understand the INTENDED system behaviour before building an automation — many integration failures stem from automating around the workflow instead of through it.

athena_suggest_workflowA

Given an integration goal, suggests the recommended API sequence, required Snowflake views, known anti-patterns to avoid, and warnings. Specifically flags when a proposed automation is fighting the intended athenaOne workflow instead of using it — a common cause of failed integrations and partner certification failures.

athena_submit_feedbackA

Submit feedback about an athenahealth interaction outcome. Call this after resolving an issue (success or failure) to help the knowledge base learn from the experience. Low-risk patterns (error resolutions, general gotchas) are automatically merged. High-risk patterns (schema discoveries, relationship changes) are queued for review. This is how the extension gets smarter over time.

athena_list_candidatesA

Lists pending knowledge base update candidates from the review queue. These are high-impact discoveries (schema corrections, relationship changes, identity patterns) that were flagged by the learning loop and need human approval before being added to the knowledge base.

athena_review_candidateA

Approve or reject a pending knowledge base update candidate. Approved candidates are promoted to the learned knowledge base with elevated confidence. Rejected candidates are marked with the rejection reason for audit.

athena_report_safety_flagA

Record that a proactive athenahealth safety rule fired during this interaction. Call this every time you flag an anti-pattern from the SKILL.md safety rules (PATIENTID=CHARTID join, missing DELETEDDATETIME filter, missing CONTEXTID, hardcoded credentials, missing rate-limit retry, etc.). One call per flag. Non-blocking — never delays your response.

athena_report_outcomeA

Report the outcome of an athenahealth-related interaction once it concludes. Call this after producing an artifact (SQL, code, diagnosis, explanation) so we can measure value delivered. One call per logical interaction. Non-blocking.

athena_command_startA

Mark the start of a slash command invocation. Call this as the first action in every athena slash command (/sql, /onboard, /diagnose, /athena-api, /review-athena, /validate, /explain, /workflow). One call per invocation. Returns a session ID that can be passed to athena_report_outcome at the end.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nous-ehr/claude_pallas_extension'

If you have feedback or need assistance with the MCP directory API, please join our Discord server