Skip to main content
Glama

Scaffold blog architecture

blog.scaffold

Generates MDX blog file specifications for Next.js App Router projects, so coding agents can create correct routes and content structures after planning.

Instructions

Specialized: App Router + MDX blog file specs when justified. Prefer qualitykit.plan first.

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": {
      "projectRoot": "<projectRoot>"
    },
    "name": "blog.scaffold"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlNo
projectRootYesAbsolute path to the website repository root
contentSystemNov1 supports MDX onlymdx
includeCategoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it says almost nothing: no indication of whether files are actually written, whether existing files are overwritten, what permissions or repo state are required, or what the caller receives back. For a scaffolding operation that likely mutates a repository, that is a substantial gap.

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

Conciseness3/5

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

It is short with no filler, but the terseness is under-specification rather than economy; the leading 'Specialized:' label and the dangling 'when justified' convey tone without content. The one load-bearing sentence (prefer qualitykit.plan) is present but buried behind a fragment.

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 no annotations, no output schema, and half the parameters undescribed, this definition should explain what the tool produces and what it touches. Instead it provides only a domain label and a routing hint, leaving an agent unable to predict the side effects or the return value of a repository-scaffolding call.

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 coverage is 50%: projectRoot and contentSystem have descriptions, while siteUrl and includeCategories are undocumented. The description mentions no parameters at all, so it adds zero meaning over the schema and does nothing to compensate for the undocumented pair — notably the purpose of siteUrl in a file-scaffolding tool and the effect of includeCategories on output.

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

Purpose3/5

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

The description identifies the domain ('App Router + MDX blog file specs'), which narrows it usefully against generic planning siblings, but it is a noun phrase with no verb — it never says whether it creates files, emits specs, or writes config. 'File specs' is ambiguous between produced artifacts and file layout.

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?

'Prefer qualitykit.plan first' gives real ordering guidance and names the alternative, which is the strongest part of the definition. However, 'when justified' is undefined, and there is no statement of when this tool is the wrong choice or what precondition (plan output?) it consumes.

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