Skip to main content
Glama

architect

Generate architectural design feedback using natural language input and maintain context with optional conversation ID through POST requests to the LLM Architect tool on the MCP Server Template platform.

Instructions

MCP server for the LLM Architect tool. Exposes resource "/llm-architect/chat" accepting POST requests with a prompt and optional conversationId, and interacts with the llm chat CLI to provide architectural design feedback while maintaining conversation context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conversationIdNoOptional conversation ID for context
inputYesInput prompt to process

Implementation Reference

  • The ARCHITECT_HANDLERS object defining the handler function for the 'architect' tool. This is the primary execution logic that validates input, checks dependencies, processes the request via handleArchitectProcess, and returns the result.
    export const ARCHITECT_HANDLERS: ToolHandlers = {
        'architect': async (request): Promise<ToolResult> => {
            try {
                const { input, conversationId } = request.params.arguments as { input: string, conversationId?: string };
                // Validate input using zod
                architectInputSchema.parse({ input, conversationId });
    
                // Ensure the 'llm' command exists
                if (!(await commandExists('llm'))) {
                    throw new Error('LLM command not found. Please ensure it is installed and in your PATH.');
                }
                const result = await handleArchitectProcess(input, conversationId);
                return {
                    toolResult: {
                        content: [{ type: 'text', text: JSON.stringify({ conversationId: result.conversationId, response: result.response }) }],
                    }
                };
            } catch (error) {
                const errorMessage = error instanceof Error ? error.message : String(error);
                throw new Error(`Failed to process input: ${errorMessage}`);
            }
        }
    };
  • Zod schema for validating the input parameters of the 'architect' tool (input string and optional conversationId). Used within the handler.
    const architectInputSchema = z.object({
        input: z.string().min(1, 'Input must not be empty'),
        conversationId: z.string().optional()
    });
  • Definition of the 'architect' tool including its name, description, and input schema, exported as part of ARCHITECT_TOOLS array.
    const ARCHITECT_TOOL: Tool = {
        name: 'architect',
        description: 'MCP server for the LLM Architect tool. Exposes resource "/llm-architect/chat" accepting POST requests with a prompt and optional conversationId, and interacts with the llm chat CLI to provide architectural design feedback while maintaining conversation context.',
        inputSchema: {
            type: 'object',
            properties: {
                input: {
                    type: 'string',
                    description: 'Input prompt to process',
                    minLength: 1
                },
                conversationId: {
                    type: 'string',
                    description: 'Optional conversation ID for context',
                    nullable: true
                }
            },
            required: ['input']
        }
    };
    
    // Export tools
    export const ARCHITECT_TOOLS = [ARCHITECT_TOOL];
  • src/index.ts:21-22 (registration)
    Incorporates the architect tools and handlers into the global ALL_TOOLS and ALL_HANDLERS used by the MCP server for tool listing and execution.
    const ALL_TOOLS = [...ARCHITECT_TOOLS]
    const ALL_HANDLERS = { ...ARCHITECT_HANDLERS }
  • Helper function that performs the core processing: cleans the input and delegates to conversation handling logic.
    async function handleArchitectProcess(input: string, conversationId?: string): Promise<{ conversationId: string, response: string }> {
        const cleanedInput = input.replace(/\n/g, ' ').trim();
        return await handleConversation(cleanedInput, conversationId);
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool 'interacts with the llm chat CLI to provide architectural design feedback while maintaining conversation context,' which implies it's a read/write operation with state persistence. However, it lacks details on authentication needs, rate limits, error handling, or what specific 'architectural design feedback' entails. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, starting with the tool's role as an MCP server and its key functionality. It uses two sentences efficiently: the first covers the resource and parameters, and the second explains the interaction with the CLI and purpose. There's minimal waste, though it could be slightly more concise by integrating the two ideas more tightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (a chat-based tool with conversation context), no annotations, and no output schema, the description is moderately complete. It explains the tool's purpose and parameters but lacks details on behavioral traits like response format, error cases, or specific feedback mechanisms. For a tool without structured output information, it should do more to compensate, but it provides a basic viable understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds some semantic context beyond the input schema. It mentions that the tool accepts 'a prompt and optional conversationId,' which aligns with the schema's 'input' (required) and 'conversationId' (optional) parameters. However, with 100% schema description coverage (both parameters have descriptions in the schema), the description doesn't provide additional meaning or usage examples. This meets the baseline of 3 for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: it's an MCP server that exposes a resource for POST requests to interact with an LLM chat CLI for architectural design feedback. It specifies the verb ('interacts with'), resource ('/llm-architect/chat'), and context ('maintaining conversation context'). However, since there are no sibling tools mentioned, it doesn't need to distinguish from alternatives, so it falls just short of a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides minimal usage guidance. It mentions that the tool accepts POST requests with a prompt and optional conversationId, but it doesn't explain when to use this tool versus other potential tools (though none are listed as siblings), nor does it provide context about when this specific architectural feedback tool is appropriate versus general chat tools. No exclusions or alternatives are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

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/stevennevins/architect-mcp-server'

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