Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AZURE_CLIENT_IDYesYour Azure application (client) ID from App registration
AZURE_TENANT_IDYesYour Azure directory (tenant) ID from App registration

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_networksA

Get all Viva Engage networks the user belongs to

get_communitiesA

Get all Viva Engage communities/groups the user is a member of in their home network

get_community_by_idA

Get details of a specific Viva Engage community by its ID

get_community_messagesB

Get all messages/posts in a specific Viva Engage community in the home network

get_threadC

Get all messages in a specific conversation thread

search_messagesA

Search for posts and messages across all communities in the home network

post_messageC

Post a new message to a Viva Engage community

reply_to_messageB

Reply to an existing message or conversation thread

get_storyline_feedA

Get the current user's Viva Engage storyline/personal feed

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct resource or action: communities are separate from messages, threads, feeds, and networks. No apparent overlap between tools like get_community_messages and get_thread, as one fetches all posts in a community and the other retrieves a specific conversation thread.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_communities, post_message, search_messages). No mixing of styles or vague verbs.

Tool Count5/5

With 9 tools covering communities, messages, threads, networks, feeds, and search, the count is well-scoped for a social engagement platform. Each tool serves a clear purpose without unnecessary redundancy.

Completeness4/5

The tool set covers core read and write operations for communities and messages, including posting and replying. However, it lacks update and delete functionality for messages, which is a minor gap for full lifecycle management.

Maintenance

ActivityInactive
ResponsivenessNo issues