Skip to main content
Glama

setup

Configure StackGuide for your project. Auto-detects project type or allows manual selection, with options for integrations and TDD preferences.

Instructions

Configure StackGuide for your project. Auto-detects project type or lets you specify one manually.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoProject path (default: current directory)
typeNoProject type to use (auto-detected if not specified)
modelNoPreferred model identifier for TDD runs (saved in .stackguide/config.json)
tokenModeNoToken profile for prompts and workflow responses
integrationsNoExternal MCP integrations to scaffold as templates
jiraIssueTypeNoDefault Jira issue type (Task, Story, Bug...)
jiraProjectKeyNoDefault Jira project key used when creating tickets from descriptions
mcpSyncTargetsNoWhere MCP template servers should be synchronized
enableAdaptiveTddNoEnable the adaptive TDD setup wizard that asks for model and integration preferences
Behavior2/5

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

No annotations exist, so the description carries full burden. It does not disclose behavioral traits such as whether it overwrites existing configuration, requires specific permissions, or is idempotent. Only mentions auto-detection vs manual specification.

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?

Two sentences, no wasted words, front-loaded with the core action. Purpose is stated immediately.

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 9 parameters, no output schema, and no annotations, the description is too brief. It fails to explain configuration effects, return values, or side effects. Incomplete for a tool of this complexity.

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?

Schema description coverage is 100%, so baseline is 3. The description adds minimal extra meaning beyond the schema (only relates to 'type' parameter). No added value for other parameters.

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

Purpose5/5

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

The description clearly states the tool configures StackGuide for a project, with auto-detection or manual type specification. This is specific and distinguishes it from sibling tools like 'init' or 'config'.

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

Usage Guidelines3/5

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

The description implies use for initial setup but provides no explicit guidance on when to use this tool vs alternatives like 'init' or 'config'. No when-not or exclusion criteria stated.

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/isucorp-taimiralain/StackGuide-MCP'

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