Skip to main content
Glama
TORIFUKUKaiou

MCP Character Count

by TORIFUKUKaiou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mcp-charcount

Simple MCP server that provides a single tool to count characters or bytes in text.

Quick start

  • Run with stdio (no PATH to python needed):

    • uv run src/mcp_charcount/server.py

  • Develop with MCP Inspector:

    • uv run mcp dev src/mcp_charcount/server.py

Related MCP server: MCP Character Counter

Tool: count_chars

  • Args: text: str, mode: "chars"|"bytes" = "chars", include_whitespace: bool = true

  • Returns: { "count": int, "mode": str, "include_whitespace": bool }

Tests

  • pytest -q (src layout is configured; install not required)

  • With uv: uv run pytest -q

Manifest

  • mcp.json is configured for this repo layout:

    • command: uv

    • args: ["run", "src/mcp_charcount/server.py"] This matches the current server which runs mcp.run(transport='stdio') when executed as a script.

Settings Example

codex

~/.codex/config.toml 

[mcp_servers.mcp-charcount]
command = "uv"
args = ["--directory", "/ABSOLUTE/PATH/TO/PARENT/FOLDER/mcp-charcount", "run", "src/mcp_charcount/server.py"]

Amazon Q Developer

~/.aws/amazonq/mcp.json 

{
  "mcpServers": {
    "local.mcp-charcount": {
      "command": "/opt/homebrew/bin/uv",
      "args": [
        "--directory",
        "/ABSOLUTE/PATH/TO/PARENT/FOLDER/mcp-charcount",
        "run",
        "src/mcp_charcount/server.py"
      ]
    }
  }
}

License: MIT

Available Tools

1 tool
count_charsA
Count the length of input text.

- mode="chars": Unicode code points count (Python len).
- mode="bytes": UTF-8 encoded byte length.
- include_whitespace: when False, whitespace characters are filtered out before counting.
ParametersJSON Schema
NameRequiredDescriptionDefault
textYes
modeNochars
include_whitespaceNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: the two counting modes (Unicode code points vs. UTF-8 bytes) and the whitespace filtering option. However, it doesn't mention performance characteristics, error handling, or output format details, leaving some behavioral aspects unclear.

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 perfectly structured and concise. It starts with a clear purpose statement, then uses bullet points to efficiently explain parameter behaviors. Every sentence earns its place with no wasted words, making it easy to scan and understand.

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?

Given the tool's moderate complexity (3 parameters, no annotations, but with an output schema), the description is reasonably complete. It explains what the tool does and parameter semantics well. Since an output schema exists, it doesn't need to describe return values. The main gap is lack of usage context, but otherwise it provides good coverage.

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

Parameters5/5

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

The description adds significant meaning beyond the input schema, which has 0% description coverage. It explains the semantics of all three parameters: 'text' is implied as input, 'mode' defines counting methods with examples, and 'include_whitespace' specifies filtering behavior. This fully compensates for the schema's lack of descriptions.

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 clearly states the tool's purpose: 'Count the length of input text.' This specifies the verb ('count') and resource ('length of input text'), making the function immediately understandable. However, with no sibling tools mentioned, there's no need for differentiation, so it doesn't reach the highest score of 5.

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 on when to use this tool versus alternatives. It explains what the tool does but offers no context about scenarios where it would be appropriate or prerequisites for use. Without sibling tools, this is less critical, but still a gap in usage guidance.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedcount_chars
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clearly defined purpose of counting characters in text.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tool names to compare against. The name 'count_chars' follows a clear verb_noun pattern.

Tool Count2/5

A single tool for a character counting server feels thin and limited in scope. While the tool is functional, the server's purpose could reasonably support additional related operations (e.g., word counting, line counting, text analysis), making the single tool count appear underdeveloped.

Completeness2/5

The server's domain appears to be text analysis or character operations, but it only offers character counting with configurable modes. There are obvious gaps, such as no tools for word counting, line counting, text transformation, or other common text processing tasks, which limits its utility.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Character Counter

    MCP-Mirror
    F
    license
    Not graded
    quality
    Not graded
    maintenance
    Provides detailed character analysis for text, counting total characters, characters without spaces, letters, numbers, and symbols through a simple MCP tool interface.
    -

  • Twitter MCP Server

    serima
    F
    license
    A
    quality
    D
    maintenance
    Provides tools for accurate Twitter/X post character counting, validation, and optimization using official counting methods. It enables users to extract entities like URLs and hashtags to ensure content fits within platform constraints.
    4
    1
    -

  • text-count-mcp-server

    yuiseki
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides tools for AI models to count characters and words in text, supporting English and other space-delimited languages.
    1
    MIT