Counting MCP Server

Overview Schema Source Related Servers Discussions Admin

count-characters

Count how many times a specific character appears in any given text. Provide the text and the character to get an exact occurrence count.

Instructions

Counts occurrences of a specific character in text

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>",
      "character": "<character>"
    },
    "name": "count-characters"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	The text to analyze
`character`	Yes	The character to count

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1Sep 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits, but it only states the basic counting operation. It does not clarify case sensitivity, whether the 'character' parameter must be a single character, or how multi-character strings are handled. These gaps could lead to incorrect invocation.

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 sentence with zero filler, front-loading the action and the target. Every word earns its place.

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

Completeness3/5

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

For a simple two-parameter tool, the schema covers parameter meanings, but there is no output schema and no explicit statement of the return value or edge-case behavior. The description is adequate for the straightforward case but leaves subtle behavior (case sensitivity, multi-character input) undefined.

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%, with both 'text' and 'character' documented in the input schema. The description adds no further semantic detail beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('counts') and names the resource ('occurrences of a specific character in text'), making the tool's purpose unambiguous. Even though no sibling tools are listed, the operation is clearly differentiated from any general text manipulation tool.

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?

There is no guidance on when to use this tool versus alternatives, and no usage context is provided. The description is a bare statement of functionality with no mention of intended scenarios, limitations, or exclusions.

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

Deploy Server

Other Tools

count-charactersB