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

Tools

Functions exposed to the LLM to take actions

NameDescription
register_serverB

Register an MCP server with metadata. Tracks health, tools, and org membership.

health_checkB

Check server health. Attempts connection, measures latency, tracks uptime history.

find_duplicatesA

Find servers with overlapping tool definitions. Uses Jaccard similarity on tool name sets.

export_configA

Export portable MCP config for Claude Desktop, Cursor, or VS Code.

get_inventoryA

List all registered servers with health and usage stats.

recommend_consolidationC

Suggest merging duplicate or overlapping servers to reduce sprawl.

check_before_installB

Pre-install report: health probe, security flags, estimated token cost, and duplicate check against your registry.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
servers

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation4/5

Tools have distinct purposes: install checks, config export, duplicate detection, inventory listing, health checks, consolidation recommendations, and registration. There is some slight overlap between find_duplicates and recommend_consolidation, but they focus on different aspects.

Naming Consistency5/5

All tool names use a consistent verb_noun pattern (check_before_install, export_config, find_duplicates, get_inventory, health_check, recommend_consolidation, register_server), with underscores separating words.

Tool Count5/5

7 tools is appropriate for a registry management server covering registration, health monitoring, duplicate detection, and configuration export. Each tool serves a clear purpose without excess.

Completeness4/5

Core lifecycle operations are covered (register, health check, inventory, duplicate detection, config export). Missing update/unregister server operations, but these are likely less critical for an MCP registry.

Maintenance

ActivityInactive
ResponsivenessNo issues