Skip to main content
Glama
rekog-labs

Counting MCP Server

by rekog-labs
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Remote MCP Tools

Install the dependencies:

npm install

Start your MCP server with:

npm run start

Your server will be running at http://localhost:3000/mcp.

You can quickly try it out with the command below:

bunx @modelcontextprotocol/inspector@0.16.2 \
  --cli http://localhost:3000/mcp \
  --transport http \
  --method tools/list

Or try it out interactively using the inspector:

bunx @modelcontextprotocol/inspector@0.16.2

Related MCP server: Toy MCP Server

Connecting to Claude Desktop

To connect your tool to Claude Desktop:

  1. Open Claude Desktop.

  2. Go to Settings > Developer > Edit Config.

  3. Add your MCP server to the configuration using mcp-proxy:

{
  "mcpServers": {
    "counting": {
      "command": "mcp-proxy",
      "args": [
        "http://localhost:3000/sse"
      ]
    }
  }
}

NOTE: mcp-proxy (repo) enables Claude Desktop (which currently supports only the stdio transport of the MCP spec) to connect to your MCP Server via HTTP+SSE protocol by translating between the two. Ensure mcp-proxy is installed and accessible in your system's PATH.

Restart Claude Desktop, and your tool will be available.

Testing It Out

Now you can ask Claude: "How many 'R's are in 'strawberry'?"

Claude should use your counting tool to provide the correct answer.

Strawberry response with Tools

Available Tools

1 tool
count-charactersB

Counts occurrences of a specific character in text

ParametersJSON Schema
NameRequiredDescriptionDefault
textYesThe text to analyze
characterYesThe character to count

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.0.1
    • First observedcount-characters
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusing it with another tool. The tool's purpose is clearly defined as counting occurrences of a specific character in text.

Naming Consistency5/5

The single tool name 'count-characters' follows a clear verb_noun pattern. Since there is only one tool, naming consistency is trivially maintained.

Tool Count4/5

One tool is slightly below the typical 3-15 range, but it is reasonable for a server dedicated to a single specific function. The narrow scope justifies having just one tool.

Completeness5/5

For the domain of counting character occurrences, the tool fully covers the intended operation with no dead ends. The server does exactly what its name and description indicate.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

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/rekog-labs/mcp-nest-getting-started'

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