Skip to main content
Glama

Plan internal links

links.plan

Suggests contextual internal links for a website repo: analyzes routes and proposed paths, then returns prioritized linking recommendations to strengthen site structure and discoverability.

Instructions

Specialized: contextual internal-link suggestions.

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

Input Schema

NameRequiredDescriptionDefault
siteUrlNo
projectRootYesAbsolute path to the website repository root
proposedPathsNoOptional proposed routes such as /blog/understanding-x
maxSuggestionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

D1.5/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but supplies none. It does not say whether the tool is read-only, whether it writes or modifies the repository, what permissions are needed, or what the return value 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.

Conciseness2/5

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

The definition is a single short fragment, but it is under-specified rather than concise. It is not front-loaded with actionable detail and lacks structure beyond a category label.

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 four-parameter planning tool with no annotations and no output schema, the description omits nearly everything an agent needs: tool scope, behavior, return shape, and parameter usage. It is not complete enough to support correct 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 coverage is 50%: projectRoot and proposedPaths have schema descriptions, but siteUrl and maxSuggestions do not. The description adds no meaning for any parameter, leaving the URI semantics and the suggestion cap unexplained beyond the schema's type/default/min/max.

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 phrase "Specialized: contextual internal-link suggestions" restates the title without a concrete verb, scope, or output form. "Contextual" and "specialized" are undefined, so it does not distinguish links.plan from sibling planning tools such as seo.plan_changes or qualitykit.plan.

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

Usage Guidelines1/5

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

No when-to-use guidance, prerequisites, or alternatives are given. An agent cannot tell when to choose links.plan over another planning tool or what conditions make projectRoot and proposedPaths appropriate.

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