Skip to main content
Glama
Sign In
forgespec-mcp

forgespec-mcp

by lleontor705
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sdd_history

Read-onlyIdempotent

Retrieve the chronological SDD phase history for a project, showing all contract transitions in order. Filter by phase, change name, or revision to trace the evolution of specifications.

Instructions

Get the SDD phase history for a project. Shows all contract transitions in chronological order.

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": "<project>"
    },
    "name": "sdd_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax entries to return
phaseNo
cursorNo
projectYesProject identifier
change_nameNo
consistencyNo
since_revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.6.0
    • addedInput schema / properties / change_name
      Added value: +{
+  "maxLength": 256,
+  "type": "string"
+}
    • addedInput schema / properties / consistency
      Added value: +{
+  "enum": [
+    "best_effort"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / cursor
      Added value: +{
+  "maxLength": 4096,
+  "type": "string"
+}
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / phase
      Added value: +{
+  "enum": [
+    "init",
+    "explore",
+    "propose",
+    "spec",
+    "design",
+    "tasks",
+    "apply",
+    "verify",
+    "archive"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / since_revision
      Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv1.2.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, covering safety. The description adds the chronological ordering detail, which is useful but minimal. It does not mention pagination, filtering behavior, or any edge cases, so it provides only mild context beyond structured data.

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 two sentences with zero fluff. It front-loads the core action and provides a brief clarifying second sentence. No unnecessary words or redundancy.

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?

With 7 parameters, no output schema, and no mention of pagination or filtering options beyond a vague 'for a project', the description is incomplete. It does not explain how to use cursor for pagination, the phase filter, or consistency mode, leaving the agent under-informed for effective invocation.

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

Parameters2/5

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

Schema description coverage is low (29%), with only project and limit having descriptions. The tool description adds no extra parameter information; it only mentions 'for a project'. With 7 parameters and several undocumented ones (phase, cursor, change_name, consistency, since_revision), the description fails to clarify their meaning or usage.

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's purpose: retrieving SDD phase history for a project, showing contract transitions in chronological order. This distinctly separates it from siblings like sdd_get or sdd_list, which would retrieve current state rather than history.

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 usage for a specific project and history retrieval, but does not explicitly state when to prefer this over other sdd_* tools or mention any exclusions. It provides context but lacks explicit alternatives or when-not-to-use guidance.

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