Skip to main content
Glama

Generate a structured outline for a topic or a text

text_outline
Read-only

Builds an outline (title, sections with headings and bullet points, optional word targets) for a topic, or from a text you give. Depth 1-3, at most 12 sections. Model output: review it before use; word targets are estimates. Input text max 10,000 characters. Related tools on this server, for a different need: text_headlines when you need to generate headlines for a text or topic in a chosen style; text_chunk when you need to generate overlapping text chunks with character offsets. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "text_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoSource text to outline (max 10,000 characters); use this or topic
depthNoHeading depth 1-3 (default 2)
topicNoTopic to outline (max 300 characters); use this or text
sectionsNoNumber of sections, 1-12 (default 5)

Output Schema

NameRequiredDescriptionDefault
noteNo
depthNo
titleNo
sectionsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / checkedAt
      Added value: +{}
    • addedOutput schema / properties / depth
      Added value: +{}
    • addedOutput schema / properties / note
      Added value: +{}
    • addedOutput schema / properties / sections
      Added value: +{}
    • addedOutput schema / properties / title
      Added value: +{}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds substantive behavior: a per-call price of $0.002 charged via x402 (USDC on Base, Solana and other networks), the fact that failed calls are not charged, that model output should be reviewed before use, and that word targets are only estimates. Those cost, auth, and quality caveats are exactly the burden the description must carry and go well beyond the annotation set.

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?

The core capability and its structural output are front-loaded in the first sentence, followed by limits, caveats, alternatives, and price in a logical order. Every clause carries information, though the pricing sentence is dense (network list) and could be trimmed without losing the cost signal.

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

Completeness5/5

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

With an output schema present, return values need no explanation, and annotations already cover the safe-read profile. The description fills the remaining gaps an agent needs to call correctly: input size ceiling, depth and section ranges, review expectation, latency-agnostic cost model, and where to go for adjacent tasks.

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

Parameters3/5

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

Schema coverage is 100%, so depth 1-3, sections 1-12, the 10,000-character text cap and the topic-vs-text exclusivity are already documented in the schema. The description restates those bounds (depth, 12 sections, 10k chars) without adding format or interaction semantics beyond what the schema provides, which is the baseline-3 case.

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

Purpose5/5

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

States a specific verb and resource ("Builds an outline") and enumerates the produced structure (title, sections with headings and bullet points, optional word targets) plus both input modes (topic or given text). The trailing related-tools sentence names text_headlines and text_chunk with their distinct purposes, so the tool is distinguishable from its closest siblings without opening any schema.

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

Usage Guidelines4/5

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

Gives clear selection context ("for a topic, or from a text you give") and explicitly routes two adjacent needs elsewhere: text_headlines for headline generation in a chosen style, text_chunk for overlapping chunks with character offsets. It stops short of stating when not to use this tool (e.g., very long documents beyond 10k chars must be pre-split), but the alternative routing is concrete.

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