Riza MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RIZA_API_KEY | Yes | Your Riza 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 |
|---|---|
| create_toolC | Create a new tool. This tool will be used to create new tools. You can use the tools you have created to perform tasks. |
| fetch_toolA | Fetch a tool, including its source code. |
| edit_toolA | Edit a tool, including its source code. Omit properties that you do not want to change. |
| execute_codeB | Execute arbitrary Typescript or Python code. |
| list_toolsA | Lists the tool definitions of all self-written tools available for use. These tools can be used by calling |
| execute_toolB | Executes a tool. This tool will be used to execute a self-written tool. |
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 6 tools
Each tool has a distinct role: create, fetch, edit, list, and execute self-written tools, plus execute_code for arbitrary ad-hoc code. The only potentially overlapping pair, execute_code and execute_tool, is clearly separated by whether the code is a saved tool or not.
All tool names follow a consistent snake_case verb_noun pattern, such as create_tool, fetch_tool, edit_tool, and execute_tool. The minor pluralization in list_tools is predictable and does not break the naming convention.
Six tools is well-suited to the server's purpose of managing and executing self-written tools. Each tool contributes a necessary operation without unnecessary bloat.
The set covers create, read, update, list, and execute, but lacks a delete/remove operation, which is a notable lifecycle gap. Additionally, list_tools references a use_tool that does not exist in the exposed tool set, though execute_tool appears to fill that role.