GPTHuman-Humanizer
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GPTHUMAN_API_KEY | Yes | Your GPTHuman 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| humanize_textA | Transforms AI-generated text into a more natural, human-sounding variant while preserving the requested tone and rewrite mode. Input must be at least 300 characters and must not exceed 2,000 words. |
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
Only one tool exists, so there is no risk of confusion between tools.
With a single tool, naming consistency is trivially perfect; the name 'humanize_text' is clear and follows a verb_noun pattern.
The server offers only one tool, which feels thin for a server dedicated to humanizing text; additional tools like detection or tone adjustment would be expected.
The tool covers basic humanization but lacks other expected operations such as tone selection, style conversion, or AI text detection, leaving significant gaps.