Riza MCP Server

create_tool

Build custom executable tools by providing TypeScript or Python code and a JSON Schema input definition. Use these generated tools to automate tasks through a secure code interpreter.

Instructions

Create a new tool. This tool will be used to create new tools. You can use the tools you have created to perform tasks.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "description": "<description>",
      "code": "<code>",
      "input_schema": "<input_schema>",
      "language": "<language>"
    },
    "name": "create_tool"
  }
}

Input Schema

Name	Required	Description
`code`	Yes	The Typescript code for the tool you are writing. The code should be a valid Typescript function named `execute` that takes one argument called `input`. When called, the `input` provided will match the schema of the `input_schema` of the tool.
`name`	Yes	The name of the tool you are writing. This is what you will use to call the tool.
`language`	Yes	The language of the tool you are writing. This must be either 'TYPESCRIPT' or 'PYTHON'.
`description`	Yes	A description of the tool you are writing. This will help you or other agents or people pick the appropriate tool in the future.
`input_schema`	Yes	The input schema for the tool. This must be provided as a valid JSON Schema object.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Aug 30, 2026

TDQS

C2.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says the tool creates something. It does not disclose side effects, persistence, permissions, validation behavior, or what happens after creation, leaving the agent with the bare meaning of the verb.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description wastes space with a redundant second sentence and a vague third sentence that does not explain the creation workflow. It would be stronger as a single focused sentence stating the tool's purpose and perhaps a key constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with five required parameters, no annotations, and no output schema, the description is under-specified. It lacks guidance on how created tools integrate with sibling tools, what the response will be, and when to use this instead of edit_tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides 100% coverage with descriptions for all five required parameters, so the baseline of 3 applies. The tool description itself adds no parameter-level meaning, but the schema compensates adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence, 'Create a new tool,' clearly states the verb and resource, and the tool name plus siblings make its distinct role as creation versus fetch/edit/list/execute evident. However, the second sentence is a tautology that restates the name and adds no new meaning.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use create_tool versus edit_tool or other siblings. It only vaguely states that created tools can be used to perform tasks, which does not help an agent decide when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server