API-get-input-schema
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.
LABSCO SUMMARY
This is a discovery shim, not a data server: nothing here returns RSS3 content, only the shape of the call that would.
The design trades tool-list size for a round trip — a client carries a single tool definition instead of a separate one for every API, and pays a schema fetch before each call, which the tool's own description asks for every time. The consequence for a reader is that the API surface is discovered at runtime through toolName rather than read off the tool list, so an agent that guesses names will fail at the shim rather than at the API.
What it is
A single-tool front door to RSS3's APIs: API-get-input-schema takes a toolName and returns the input schema for that API, which its own description says to fetch before every call.
What you get
- A schema lookup by name: API-get-input-schema returns the input schema for the API named in
toolName, so the argument shape is read from the server rather than assumed. - A single entry point rather than a separate tool for every API: the APIs reachable this way are addressed through the
toolNameargument, so the client's tool list stays at one definition however many APIs sit behind it.
Requirements
No credentials are configured. A call needs the name of the API you intend to use, since toolName is the only argument the schema lookup takes.
Setup effort
One command — npx mcp-server-rss3
USE CASES
01
Checking what an API call expects before you make it
Ask for the schema by name and build the call from what comes back, instead of guessing the argument shape.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-server-rss3": {
"command": "npx",
"args": [
"mcp-server-rss3"
]
}
}
}npx
TERMINAL
npx mcp-server-rss3
