Skip to main content
Glama

speckit_constitution

Establish project principles and foundational guidelines using guided prompts to define core values and constraints for project specifications.

Instructions

Establish project principles using spec-kit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the logic for the 'speckit_constitution' tool. It returns a standardized message prompting the model to read or create the project constitution file.
    private async handleConstitution(commandsPath: string) {
        return {
            messages: [
                {
                    role: "user",
                    content: {
                        type: "text",
                        text: `Please read the project constitution at 'commands/speckit.constitution'. 
                        [Note that if this file exists, it is generally in the current directory's "./.specify/memory/constitution.md" File]
                         [It's important. You must read it]. 
                         If the file is missing or empty, create it with principles focused on code quality, testing standards, user experience consistency, and performance requirements. If it exists, review and use it as the foundation.`,
                    },
                },
            ],
        };
    }
  • src/index.ts:136-143 (registration)
    Registration of the 'speckit_constitution' tool in the ListToolsRequestSchema handler, including name, description, and empty input schema.
    {
        name: "speckit_constitution",
        description: "Establish project principles using spec-kit",
        inputSchema: {
            type: "object",
            properties: {},
        },
    },
  • Dispatch case in the CallToolRequestSchema handler that routes the tool call to the handleConstitution method.
    case "speckit_constitution":
        result = await this.handleConstitution(commandsPath);
        break;
  • Input schema definition for the 'speckit_constitution' tool, which accepts no parameters.
    inputSchema: {
        type: "object",
        properties: {},
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Establish project principles', implying a creation or setup operation, but doesn't clarify if this is a read-only or mutative action, what permissions are needed, or how the tool behaves (e.g., output format, side effects). This leaves significant gaps in understanding the tool's behavior.

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

Conciseness5/5

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

The description is a single, efficient sentence: 'Establish project principles using spec-kit'. It is front-loaded with the core action and resource, with no wasted words or redundancy, making it highly concise and well-structured.

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

Completeness2/5

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

Given the tool's purpose of establishing principles (which could involve complex decision-making), the lack of annotations, output schema, and detailed behavioral context makes the description incomplete. It doesn't explain what 'establish' entails, what output to expect, or how it integrates with the spec-kit system, leaving the agent with insufficient information for effective use.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented. The description doesn't add parameter details, which is appropriate since there are none. Baseline for 0 parameters is 4, as the description needn't compensate for missing parameter information.

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 action ('Establish') and resource ('project principles') using the tool 'spec-kit'. It distinguishes from siblings like speckit_implement, speckit_plan, speckit_specify, and speckit_tasks by focusing on principles rather than implementation, planning, specification, or task management. However, it doesn't explicitly differentiate itself from these siblings, which prevents 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 no guidance on when to use this tool versus its siblings. It mentions 'Establish project principles' but doesn't specify contexts, prerequisites, or alternatives. Without annotations or explicit usage instructions, the agent has minimal direction for tool selection.

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

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/anyiba/spec-kit-mcp'

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