Skip to main content
Glama
Sign In
Specky

Specky

by gbb-acelerators
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Check Spec-Code Sync

sdd_check_sync
Read-onlyIdempotent

Compare specification requirements against implementation files to produce a drift report identifying missing or implemented requirements.

Instructions

Compares specification requirements against implementation files and returns a drift report showing which requirements are implemented and which are missing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sdd_check_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
spec_dirNoSpec directory path (relative to workspace root).specs
code_pathsNoPaths to implementation files to check against spec
feature_numberNoFeature number (zero-padded, e.g. '001')001

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.4.0-rc.14

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds context that output is a drift report, consistent with annotations. No contradictions.

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?

Single sentence that is clear and to the point. No wasted words or repetition.

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

Completeness4/5

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

No output schema, but description mentions drift report. Additional detail about report format or contents would 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?

All three parameters have schema descriptions (100% coverage). Description does not add new semantic information beyond the schema.

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?

Description clearly states the tool compares specification requirements against implementation files and returns a drift report. This specific verb+resource combination distinguishes it from sibling check tools like sdd_check_access or sdd_check_ecosystem.

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?

Implies usage for checking spec-code sync, but no explicit guidance on when to use vs alternatives like sdd_scan_codebase or sdd_run_analysis. No when-not-to-use conditions mentioned.

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