mcp-counter-server
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| counter_incrementA | Increment a counter by a specified amount (default: 1). Creates the counter if it doesn't exist. Use this to track iterations, processed items, or any counting task. |
| counter_getA | Get the current value and metadata for a specific counter. |
| counter_resetA | Reset a counter back to 0. The counter continues to exist and its history is preserved. |
| counter_listA | List all active counters with their current values and metadata. |
| counter_historyA | Get the operation history for a specific counter, showing all increments, decrements, and resets. |
| counter_deleteA | Permanently delete a counter and all its history. |
| counter_parse_and_applyA | Parse counter tags from text and apply all operations in order. Supports multiple tag formats: Full syntax: [-counter:ID:+N-] or [-c:ID:+N-] for increment/decrement, [-counter:ID:reset-], [-counter:ID:delete-], [-counter:ID:set:N-]. Shorthand syntax (explicit numbers required): [+N:ID] for increment, [-N:ID] for decrement, [reset:ID], [delete:ID], [set:N:ID]. Examples: [+5:files], [-3:errors], [reset:temp], [set:100:progress]. Processes all tags sequentially and returns final counter states. |
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 7 tools
Tools are mostly distinct: increment, reset, delete, get, list, and history each target a unique operation. However, counter_parse_and_apply can also perform increment, reset, delete, and set actions, creating some overlap with the direct tools, though it is clearly scoped as a text-parsing batch operation.
All tools follow a consistent counter_<verb> pattern, using snake_case for multi-word verbs like parse_and_apply. The naming is uniform and predictable, making it easy to infer the tool's function from its name.
With 7 tools, the server is well-scoped for a counter management domain. Each tool serves a distinct operational need without excessive overlap or redundancy, striking a balance between completeness and simplicity.
The core counter lifecycle is well covered: create (via increment), read (get/list), update (increment/reset), and delete. However, direct decrement and set-to-arbitrary-value operations are missing, requiring agents to use counter_parse_and_apply with text, which is an awkward workaround for simple cases.