Skip to main content
Glama

Plan SEO changes

seo.plan_changes

Plan technical SEO file specifications for a Next.js repository using its project root, optional site URL, and optional blog recommendation flag.

Instructions

Secondary: technical SEO file specs. Prefer qualitykit.fix / qualitykit.plan.

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": "seo.plan_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlNo
projectRootYesAbsolute path to the website repository root
includeBlogHintsNoInclude a high-level blog recommendation when justified

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden and discloses essentially nothing. It does not say whether the tool writes files or only produces a plan, whether it requires network access, what happens to existing configs, or what the response contains — and there is no output schema to compensate.

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 it is two telegraphic fragments rather than a structured definition. Brevity here comes from under-specification rather than from tight editing.

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

Completeness1/5

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

For a planning tool with three parameters, one required, no annotations, and no output schema, the description should explain what a 'plan' is and what it touches. Nothing about inputs, outputs, or side effects is covered.

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 moderate (67%): projectRoot and includeBlogHints are documented in the schema, while siteUrl has no description beyond its URI format. The description adds no meaning to any of the three parameters, so it does not compensate for the gap.

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

Purpose2/5

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

The description is a fragment ('Secondary: technical SEO file specs') that never states the verb or what planning actually produces. An agent must infer from the name 'seo.plan_changes' alone that this generates a change plan; the text only hints at the domain (technical SEO files).

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?

It does route the agent away from this tool by naming two preferred siblings (qualitykit.fix / qualitykit.plan) and labelling itself 'Secondary'. However, it never states the condition under which this tool IS the right choice, so the when-to-use side of the guidance is missing.

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