Skip to main content
Glama

Sitemap to outline

sitemap_to_outline
Read-only

Convert a sitemap into an outline. Give input as a list of URLs or paths (one per line; query strings and fragments are dropped) or an indented tree, and optionally format (numbered, markdown, indent). URL lists are folded into a tree under Home, with labels guessed from slugs (placeholders for real titles). Returns the outline plus notes: sections that exist only as parents of other URLs (no page of their own), ID segments that need names, depth over 4, a branch with more than 9 children, and single-child sections. Up to 2000 lines.

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": {
      "input": "<input>"
    },
    "name": "sitemap_to_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesURLs or paths, one per line, or an indented tree
formatNonumbered (default), markdown or indent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real substance on top: query strings and fragments are dropped, URL lists are folded under a Home root, slugs become placeholder labels, and there is a 2000-line cap. Because there is no output schema, the enumerated list of returned notes (parent-only sections, unnamed ID segments, depth over 4, >9 children, single-child sections) carries useful weight.

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

Conciseness4/5

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

Purpose is front-loaded in the first sentence, then input, then output, then limit — a sensible order with no filler. The note enumerations make it dense but each clause adds distinct information an agent would otherwise have to discover by trial.

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

Completeness4/5

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

With no output schema, the description does the necessary work of describing what comes back, including the diagnostics attached to the outline, and it discloses the 2000-line input ceiling. What is missing is only sibling routing — nothing an agent needs to invoke the tool correctly is absent.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining the accepted string format ('one per line') and the normalization rule that query strings and fragments are stripped, plus that URL lists get restructured into a tree. It adds meaning beyond the schema's terse 'URLs or paths, one per line, or an indented tree'.

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

Purpose4/5

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

States a specific verb and resource: 'Convert a sitemap into an outline'. The purpose is unmistakable and readable without opening the schema, but it never distinguishes itself from adjacent siblings such as site_heading_outline or url_structure_review, leaving the agent to infer the difference.

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?

Input shape ('a list of URLs or paths ... or an indented tree') implies when the tool is applicable, but there is no explicit when-to-use or when-not, and no mention of the nearest alternative tools. Usage is inferred rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources