Skip to main content
Glama
xiaolai

Claude Writer's Aid MCP

by xiaolai
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

suggest_reorganization

Improve manuscript organization by suggesting structural changes to enhance coherence, flow, or complexity based on your current content structure.

Instructions

Suggest better content organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathNoPath to manuscript directory (defaults to current directory)
current_structureNoDescription of current structure
optimizationNoOptimization goal

Implementation Reference

  • src/tools/WriterToolHandlers.ts:161-174 (handler)
    The main execution logic for the 'suggest_reorganization' tool. It analyzes duplicates and provides reorganization suggestions based on hardcoded logic.
    private async suggestReorganization(_args: Record<string, unknown>) {
  // Get duplicate analysis
  const duplicates = await this.writersAid.findDuplicates({
    similarityThreshold: 0.7,
  });

  return {
    suggestions: [
      "Consider consolidating duplicate content",
      "Review section balance for better flow",
    ],
    duplicates: duplicates.length,
  };
}
  • src/tools/WriterToolDefinitions.ts:87-102 (schema)
    The input schema defining parameters for the 'suggest_reorganization' tool.
    {
  name: "suggest_reorganization",
  description: "Suggest better content organization",
  inputSchema: {
    type: "object",
    properties: {
      project_path: { type: "string", description: "Path to manuscript directory (defaults to current directory)" },
      current_structure: { type: "string", description: "Description of current structure" },
      optimization: {
        type: "string",
        enum: ["coherence", "flow", "complexity"],
        description: "Optimization goal",
      },
    },
  },
},
  • src/tools/WriterToolHandlers.ts:28-29 (registration)
    The switch case in handleTool that registers and dispatches to the suggestReorganization handler.
    case "suggest_reorganization":
  return this.suggestReorganization(args);
  • src/tools/WriterToolDefinitions.ts:87-102 (registration)
    The tool definition object in writerToolDefinitions array used for MCP tool registration.
    {
  name: "suggest_reorganization",
  description: "Suggest better content organization",
  inputSchema: {
    type: "object",
    properties: {
      project_path: { type: "string", description: "Path to manuscript directory (defaults to current directory)" },
      current_structure: { type: "string", description: "Description of current structure" },
      optimization: {
        type: "string",
        enum: ["coherence", "flow", "complexity"],
        description: "Optimization goal",
      },
    },
  },
},

Tool Definition Quality

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Suggest' implies a read-only, advisory operation, but the description doesn't clarify if it modifies files, requires specific permissions, has side effects, or provides output format. For a tool with 3 parameters and no annotations, this leaves significant behavioral gaps.

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

Conciseness5/5

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

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core purpose and appropriately sized for a tool with clear parameters in the schema. Every word earns its place without redundancy.

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

Completeness2/5

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

Given 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like what the suggestion output looks like, potential limitations, or how it interacts with the manuscript directory. For a tool that likely provides advisory content reorganization, more context is needed to guide effective use.

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 parameters are well-documented in the schema itself. The description adds no additional meaning about parameters beyond what's in the schema (e.g., it doesn't explain 'optimization' goals like 'coherence' vs 'flow'). With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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

Purpose3/5

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

The description 'Suggest better content organization' states a general purpose but lacks specificity. It mentions the action ('suggest') and resource ('content organization'), but doesn't specify what type of content (manuscript files based on schema) or how it differs from similar tools like 'validate_structure' or 'generate_outline' in the sibling list. The purpose is clear but vague about scope and differentiation.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. With siblings like 'validate_structure', 'generate_outline', and 'find_related_sections' that might overlap in content organization tasks, the description offers no context about appropriate use cases, prerequisites, or exclusions. Usage is implied from the tool name alone.

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

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/xiaolai/claude-writers-aid-mcp'

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