MCP Character Counter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| count-characters-in-textC | Count characters in a text |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is singular and clearly defined, eliminating any ambiguity in selection.
The single tool name follows a clear verb_noun pattern (count-characters-in-text), and with only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool is too few for most practical server purposes, making the server feel thin and limited. While it might suffice for a trivial utility, it lacks the depth expected for broader functionality.
The tool covers its stated purpose of counting characters, but the server's scope is minimal. There are no obvious gaps for this narrow domain, but the surface is inherently limited and may not support more complex workflows.