Skip to main content
Glama
ampcome-mcps

Riza MCP Server

by ampcome-mcps

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RIZA_API_KEYYesYour 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 use_tool with the name and input.

execute_toolB

Executes a tool. This tool will be used to execute a self-written tool.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness3/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues