Text-Toolkit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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 |
|---|---|
| case_to_camelC | Convert text to camelCase |
| case_to_pascalC | Convert text to PascalCase |
| case_to_snakeC | Convert text to snake_case |
| case_to_kebabC | Convert text to kebab-case |
| case_to_constantB | Convert text to CONSTANT_CASE |
| case_to_dotC | Convert text to dot.case |
| case_to_noC | Convert text to no case |
| case_to_pascal_snakeC | Convert text to Pascal_Snake_Case |
| case_to_pathC | Convert text to path/case |
| case_to_sentenceC | Convert text to Sentence case |
| case_to_trainC | Convert text to Train-Case |
| case_to_capitalC | Convert text to Capital Case |
| encode_base64C | Encode text to Base64 |
| decode_base64C | Decode Base64 to text |
| encode_urlC | Encode text for URLs |
| decode_urlB | Decode URL-encoded text |
| encode_htmlC | Encode HTML entities |
| decode_htmlC | Decode HTML entities |
| format_jsonC | Format and beautify JSON |
| format_xmlC | Format and beautify XML |
| format_sqlC | Format and beautify SQL |
| format_htmlC | Format and beautify HTML |
| count_charactersC | Count characters in text |
| count_wordsC | Count words in text |
| count_linesC | Count lines in text |
| analyze_readabilityC | Calculate readability metrics |
| string_trimC | Trim whitespace from text |
| string_substringC | Extract a substring |
| string_replaceD | Replace text |
| string_splitC | Split text into an array |
| string_joinC | Join an array into text |
| generate_uuidD | Generate a UUID |
| validate_uuidC | Validate a UUID |
| generate_md5C | Generate MD5 hash |
| generate_sha1C | Generate SHA-1 hash |
| generate_sha256C | Generate SHA-256 hash |
| generate_sha512C | Generate SHA-512 hash |
| generate_hmacD | Generate HMAC hash |
| generate_lorem_ipsumC | Generate lorem ipsum text |
| regex_testC | Test a regex pattern against text |
| regex_replaceC | Replace text using a regex pattern |
| regex_extractC | Extract matches using a regex pattern |
| regex_splitC | Split text using a regex pattern |
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 43 tools
Every tool has a clearly distinct purpose with no ambiguity. The case conversion tools target specific case formats, encoding/decoding tools handle different formats, and string operations are well-separated. Even similar-sounding tools like string_replace and regex_replace are clearly differentiated by their descriptions.
All tools follow a consistent verb_noun or noun_verb pattern with snake_case throughout. The naming is highly predictable: case_to_*, count_*, decode_*, encode_*, format_*, generate_*, regex_*, string_*, and validate_* patterns create excellent consistency.
43 tools is excessive for a text processing server. While the domain is broad, many tools could be consolidated (e.g., 13 case conversion tools could be a single parameterized tool). The count feels bloated and will overwhelm agents with too many similar options.
The tool surface is remarkably complete for text processing. It covers case conversion, counting, encoding/decoding, formatting, hashing, generation, regex operations, string manipulation, and validation. No obvious gaps exist for common text manipulation needs.