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
ask_hermesB

Send a prompt to Hermes Agent and get its response. Supports multi-turn via session_key.

hermes_sendC

Send a message through Hermes to a chat platform (Telegram, Discord, etc.)

hermes_channelsC

List available Hermes messaging channels/platforms

coco_healthB

Check MCP CoCo bridge and Hermes Agent health status

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 4 tools

Disambiguation4/5

ask_hermes (prompt/response with the agent) and hermes_send (push a message to a chat platform) are the only pair that could be confused, but the descriptions draw a reasonable line between conversational prompting and outbound messaging. hermes_channels and coco_health are clearly distinct from both.

Naming Consistency2/5

The set mixes verb-first (ask_hermes) with noun-first (hermes_send, hermes_channels, coco_health) and inconsistent prefixes (hermes_ vs coco_). Names are readable but there is no predictable pattern an agent can rely on.

Tool Count4/5

Four tools is small but each one covers a distinct capability of a bridge/agent server (prompt, outbound message, channel discovery, health). It sits just below a comfortable scope since there is little room for session or message-management operations.

Completeness3/5

Core operations exist, but there is no way to inspect or manage sessions (list/reset), no history or inbound message read from channels, and no channel-level configuration. Agents will hit dead ends when they need to review or clean up prior Hermes conversations.