Skip to main content
Glama

Add Project Section

add_project_section

Add and position new sections in project main.md files for clear and organized documentation. Ideal for introducing topics, expanding guidelines, or creating structured content groups with flexible placement options.

Instructions

Add a new section to the project main.md file with precise positioning control.

When to use this tool:

  • Introducing new topics or guidelines to project

  • Expanding project documentation systematically

  • Adding configuration sections

  • Creating new instruction categories

  • Organizing content into new logical groups

Key features:

  • Flexible positioning (before/after/end)

  • Maintains document structure and flow

  • Non-destructive addition

  • Reference-based positioning for precision

You should:

  1. Choose meaningful section headers with "## " prefix

  2. Decide optimal position for the new section

  3. Use reference_header for precise placement

  4. Keep sections focused on single topics

  5. Follow existing section naming conventions

  6. Consider document flow and readability

  7. Add sections progressively, not all at once

DO NOT use when:

  • Section already exists (use update_project_section)

  • Content belongs in existing section

  • Unsure about section organization

Position options: "before", "after", "end" (default) Returns: {success: bool, message?: str, error?: str}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe content for the new section
positionNoWhere to insert the section (default: "end")
project_idYesThe project identifier
reference_headerNoThe section header to use as reference point for before/after positioning
section_headerYesThe new section header (e.g., "## Configuration")
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: 'Non-destructive addition' (safety), 'Maintains document structure and flow' (system behavior), 'Flexible positioning' (capabilities), and 'Returns: {success: bool, message?: str, error?: str}' (output format). It doesn't mention rate limits or authentication needs, but covers most essential aspects.

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 description is well-structured with clear sections (When to use, Key features, You should, DO NOT use, Position options, Returns) and front-loads the core purpose. While somewhat lengthy, each section earns its place by providing valuable guidance rather than redundant information.

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?

For a tool with 5 parameters, no annotations, and no output schema, the description provides excellent completeness. It covers purpose, usage guidelines, behavioral traits, parameter context, and explicitly documents the return format. Given the complexity and lack of structured metadata, this description leaves few gaps for the agent.

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 description coverage is 100%, so the baseline is 3. The description adds some value by explaining 'Position options: "before", "after", "end" (default)' and suggesting 'Use reference_header for precise placement' in the guidelines, but doesn't provide significant additional parameter meaning beyond what the schema already documents.

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?

The description clearly states the tool 'adds a new section to the project main.md file with precise positioning control.' It specifies the exact resource (project main.md file), action (add section), and distinguishes from sibling tools like update_project_section and remove_project_section by emphasizing creation rather than modification or deletion.

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

Usage Guidelines5/5

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

The description provides explicit 'When to use this tool' with 5 specific scenarios and 'DO NOT use when' with 3 clear exclusions, including naming the alternative tool (update_project_section). This gives comprehensive guidance on when to choose this tool versus alternatives.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sven-borkert/knowledge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server