ryterpro-mcp
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| humanize_textD | Humanize text using the Ryter Pro API. |
| ryterpro_api_infoA | Return Ryter Pro MCP server configuration and documentation links. |
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 2 tools
The two tools serve clearly distinct purposes: one performs text humanization, the other provides API configuration and documentation. There is no overlap or ambiguity.
Mostly consistent with 'humanize_text' following a verb_noun pattern, while 'ryterpro_api_info' is more noun-oriented. The deviation is minor and both names are clear.
With only 2 tools, the server feels thin for a text-processing API, but the scope is narrow enough that the count is acceptable.
The core functionality of humanizing text is covered, and the info tool provides necessary context. Minor gaps like batch processing or configuration options are not essential for the stated purpose.