Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoThe port number for the MCP server to listen on. Can also be set via --port or -p command line flag.3000

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
service_statusB

Return the MCP server metadata and uptime.

refactoring_mcp_list_documentsB

List the published Refactoring MCP guidance documents.

refactoring_mcp_get_documentB

Fetch a Refactoring MCP document by key.

refactoring_mcp_get_bundleB

Return all Refactoring MCP guidance documents in one bundle.

refactoring_mcp_generate_promptB

Generate a protocol or governance prompt using the Refactoring MCP builders and persist the output.

refactoring_mcp_list_promptsB

Return metadata for all prompts stored in the MCP server.

refactoring_mcp_get_promptB

Retrieve a stored Refactoring MCP prompt by ID.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: generate_prompt creates new prompts, get_bundle retrieves all documents, get_document fetches a specific document, get_prompt retrieves a specific prompt, list_documents lists documents, list_prompts lists prompts, and service_status provides server metadata. There is no overlap in functionality, making tool selection unambiguous.

Naming Consistency4/5

Six of the seven tools follow a consistent 'refactoring_mcp_verb_noun' pattern (e.g., refactoring_mcp_generate_prompt, refactoring_mcp_list_documents), which is highly predictable. However, 'service_status' deviates from this pattern by using a different prefix and structure, slightly reducing consistency.

Tool Count5/5

With 7 tools, the count is well-scoped for a refactoring MCP server focused on document and prompt management. Each tool serves a specific role (e.g., generation, retrieval, listing, status), and none appear redundant, making the set appropriately sized for its domain.

Completeness4/5

The tool set covers core operations for managing refactoring MCP documents and prompts, including listing, retrieving, generating, and bundling. A minor gap exists in the lack of update or delete tools for documents or prompts, which could limit lifecycle management, but agents can likely work around this with the provided tools.