Skip to main content
Glama
Sign In
Specky

Specky

by gbb-acelerators
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Discover Project Requirements

sdd_discover
Idempotent

Generates 7 structured discovery questions for your project idea, covering scope, users, constraints, integrations, performance, security, and deployment.

Instructions

Returns 7 structured discovery questions tailored to your project idea. Covers: scope, users, constraints, integrations, performance, security, and deployment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_idea": "<project_idea>"
    },
    "name": "sdd_discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
spec_dirNoSpec directory path (relative to workspace root).specs
project_ideaYesDescription of the project idea
feature_numberNoFeature number (zero-padded, e.g. '001')001
codebase_summaryNoOutput from sdd_scan_codebase for context

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.4.0-rc.14

TDQS

A3.7/5.0
Behavior3/5

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

Annotations indicate idempotentHint=true and destructiveHint=false, but readOnlyHint=false, which is ambiguous. The description does not clarify side effects (e.g., whether it modifies state or is purely read). No contradiction with annotations.

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, front-loaded with key purpose, no redundant information. Efficient and clear.

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?

The description explains the output structure but lacks details on how auxillary parameters (spec_dir, codebase_summary, feature_number) influence the questions or behavior. With no output schema, more context on return value could improve completeness.

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 coverage is 100% with descriptions for all 4 parameters. The tool description adds context about output categories but does not elaborate how each parameter affects the questions. Baseline 3 is appropriate.

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 returns 7 structured discovery questions tailored to the project idea, covering specific categories. This distinguishes it from siblings that handle later phases or different tasks.

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 during initial project discovery but does not explicitly state when to use it versus alternatives like sdd_clarify or sdd_research. No exclusions or when-not-to-use guidance provided.

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

Deploy Server

Other Tools