RSS3 MCP Server
OfficialServer 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 |
|---|---|
| API-get-input-schemaA | Get the input schema for a given API. We should always use this tool to get the input schema for a given API before calling the API. |
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
With only one tool, there is no possibility of ambiguity between tools.
With a single tool, naming inconsistency is not applicable; the pattern is internally consistent.
A single tool for a server that likely should have many operations (RSS3 protocol) seems severely under-scoped.
The server provides only a meta-tool to get input schemas, with no actual domain operations, making it severely incomplete.