Skip to main content
Glama

check_readability

Analyze readability metrics for manuscripts to assess text complexity and improve writing clarity.

Instructions

Analyze readability metrics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathNoPath to manuscript directory (defaults to current directory)
file_pathNoSpecific file to analyze
metricsNoMetrics to calculate

Implementation Reference

  • Handler function that extracts file_path from args and delegates to WritersAid.analyzeReadability
    private async checkReadability(args: Record<string, unknown>) {
      const filePath = args.file_path as string | undefined;
    
      return this.writersAid.analyzeReadability(filePath);
    }
  • Input schema definition for the check_readability tool
    {
      name: "check_readability",
      description: "Analyze readability metrics",
      inputSchema: {
        type: "object",
        properties: {
          project_path: { type: "string", description: "Path to manuscript directory (defaults to current directory)" },
          file_path: { type: "string", description: "Specific file to analyze" },
          metrics: {
            type: "array",
            items: { type: "string" },
            description: "Metrics to calculate",
          },
        },
      },
    },
  • Tool name registration in the handleTool switch statement dispatcher
    case "check_readability":
      return this.checkReadability(args);
  • Core readability analysis implementation that loads files, calculates metrics using helper methods
    async analyzeReadability(filePath?: string): Promise<ReadabilityMetrics[]> {
      const files = filePath
        ? [await this.storage.getFile(filePath)]
        : await this.storage.getAllFiles();
    
      const validFiles = files.filter((f) => f !== null);
      const results: ReadabilityMetrics[] = [];
    
      for (const file of validFiles) {
        const metrics = this.calculateMetrics(file.content, file.file_path);
        results.push(metrics);
      }
    
      return results;
    }
  • Delegation method in WritersAid that forwards to ReadabilityAnalyzer
    async analyzeReadability(filePath?: string) {
      return this.readabilityAnalyzer.analyzeReadability(filePath);
    }
Behavior2/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. 'Analyze readability metrics' suggests a read-only operation, but it doesn't specify what the analysis entails, what format the results take, whether it modifies any files, or what permissions might be required. For a tool with 3 parameters and no annotation coverage, this is insufficient behavioral context.

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 maximally concise at just three words. It's front-loaded with the essential information and contains zero wasted words or unnecessary elaboration. This is an excellent example of efficient communication.

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 the tool has 3 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what readability metrics are calculated, what the output format looks like, or how the analysis is performed. For an analysis tool with multiple configuration options, more context is needed to understand what the tool actually does beyond the basic verb.

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?

With 100% schema description coverage, all three parameters are already documented in the input schema. The description doesn't add any additional meaning about the parameters beyond what the schema provides. It doesn't explain what types of readability metrics are available, what the default behavior is when parameters are omitted, or how project_path and file_path interact.

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?

The description 'Analyze readability metrics' clearly states the verb (analyze) and resource (readability metrics), making the tool's purpose immediately understandable. However, it doesn't specifically differentiate this tool from its many siblings that also perform analysis functions (like analyze_link_graph, find_duplicates, etc.), which prevents a perfect score.

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?

The description provides no guidance about when to use this tool versus alternatives. With 35 sibling tools on the server, many performing various types of analysis, there's no indication of what makes this tool distinct or when it should be chosen over similar tools like get_writing_stats or validate_structure.

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