Skip to main content
Glama

QualityKit plan

qualitykit.plan

Generates content and architecture plans for a website: content briefs, blog scaffolding, schema markup, and internal link opportunities. Returns advise-only guidance your coding agent can apply.

Instructions

Content and architecture opportunities: briefs, blog scaffold plan, schema, internal links. Advise-only.

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": "qualitykit.plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlNo
includeBlogNo
projectRootYesAbsolute path to the website repository root

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description does carry the safety burden, and 'Advise-only' usefully discloses that no changes are applied, which is the key behavioral fact for a planning tool. However, it does not explain why projectRoot (an absolute repo path) is required for an advise-only tool, whether any files or artifacts are produced, or what the plan output looks like.

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 and front-loads the output categories, but it is written as a telegraphic noun-phrase list rather than a sentence, so the brevity costs clarity rather than serving it. Nothing is wasted, but the compression leaves the core action unstated.

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?

For a multi-domain planning tool with no annotations, no output schema and only a third of parameters described, the definition does far too little. An agent cannot determine what it receives back, whether artifacts are written to projectRoot, or how it differs from the many sibling planners listed.

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 only 33%: projectRoot is documented in the schema while siteUrl and includeBlog (default true) are not, and the description adds no parameter meaning at all. It never explains how siteUrl relates to projectRoot or what includeBlog actually toggles, leaving two parameters effectively undocumented.

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 enumerates outputs (briefs, blog scaffold plan, schema, internal links) but never states a verb, so it is unclear whether the tool generates, aggregates, or merely lists these opportunities. The 'plan' suffix and the output list hint at a planning/aggregation tool, but the agent must guess its actual action relative to siblings like links.plan, schema.plan and content.brief that it name-drops.

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

Usage Guidelines2/5

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

'Advise-only' signals a constraint rather than a when-to-use rule, and there is no guidance on when this tool is preferred over the sibling planners it appears to overlap with. No prerequisites, no exclusions, no alternative routing are given.

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