MCP Toolkit
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 | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| json_inspectC | Validate JSON and inspect its structure. |
| text_analyzeC | Count words, characters, and lines in text. |
| sha256_hashA | Compute a SHA-256 hex digest for UTF-8 text. |
| base64_convertA | Encode UTF-8 text to Base64 or decode strict Base64 into UTF-8. |
| json_formatC | Pretty-print or minify a JSON string. |
| timestamp_convertA | Convert an ISO 8601 timestamp or Unix milliseconds to UTC ISO and Unix seconds/milliseconds. |
| json_pointerC | Look up a value in JSON using an RFC 6901 JSON Pointer. |
| url_encodeC | Percent-encode or decode a URL component. |
| url_inspectB | Parse an HTTP(S) URL without fetching it. |
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 9 tools
Each tool targets a distinct operation, and the json_* family is reasonably separated into inspect (structure/validation), format (pretty-print/minify), and pointer (value lookup). Minor friction remains between json_inspect and json_format since both parse JSON, and the encode/decode pairs (base64_convert, url_encode) require reading descriptions to know direction is toggled by a flag.
Nearly all names follow a consistent snake_case subject_verb pattern (json_inspect, text_analyze, url_encode, timestamp_convert). The exceptions are json_pointer, which is noun_noun with no verb, and sha256_hash, where the verb is inverted, but both remain readable and unambiguous.
Nine tools is well within the ideal 3-15 range and every tool maps to a distinct, frequently needed utility operation. Nothing feels padded or redundant within the set.
The surface covers common text/JSON/encoding/timestamp/URL chores with both encode and decode directions for Base64 and URL, plus URL and JSON inspection. Gaps exist for adjacent frequent needs like other hash algorithms (MD5/SHA-1), HMAC, UUID generation, or regex operations, but core workflows have no dead ends.