Kuro

Get own recipe

get_own_recipe

Read-onlyIdempotent

Read one recipe you own, whole: the authored arrangement (config) on an arm row, the doctrine (writer) beside it on a reprompt row, or the private workflow (definition) on a run row — plus where it stands with the catalog (submission), whether a curator restricted it, and its public page once published. Use this before update_recipe — a patch replaces config, writer or definition whole. A run row's definition, saved alone as JSON, is a workflow file Kuro Desktop opens.

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": {
      "recipe_id": "<recipe_id>"
    },
    "name": "get_own_recipe"
  }
}

Input Schema

Name	Required	Description	Default
`recipe_id`	Yes

Output Schema

Name	Required	Description	Default
`recipe`	Yes
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed27 schema fields changedNov 4, 2026

addedOutput schema / properties / recipe / properties / recipe / description

Added value: +"A template that asks a few questions and makes something."

addedOutput schema / properties / recipe / properties / recipe / properties / action / description

Added value: +"`arm` makes one generation from your answers; `reprompt` does too, with a model writing the prompt from them; `run` starts a multi-step run (`GET /v1/runs/{id}`). New values may be added."

changedOutput schema / properties / recipe / properties / recipe / properties / action / enum

Previous value: -[
-  "arm",
-  "run",
-  "reprompt"
-]New value: +[
+  "arm",
+  "reprompt",
+  "run"
+]

removedOutput schema / properties / recipe / properties / recipe / properties / allowed_models
```
Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
```
addedOutput schema / properties / recipe / properties / recipe / properties / app_url / $ref
```
Added value: +"#/properties/recipe/properties/recipe/properties/cover_url/anyOf/0"
```
removedOutput schema / properties / recipe / properties / recipe / properties / app_url / format
```
Removed value: -"uri"
```
removedOutput schema / properties / recipe / properties / recipe / properties / app_url / type
```
Removed value: -"string"
```
removedOutput schema / properties / recipe / properties / recipe / properties / arrangement
```
Removed value: -{}
```

addedOutput schema / properties / recipe / properties / recipe / properties / choices

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "help": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "key": {
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "max_picks": {
+        "type": "integer"
+      },
+      "options": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "label": {
+              "type": "string"
+            },
+            "value": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "value",
+            "label"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "shown_when": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "choice": {
+                "type": "string"
+              },
+              "values": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              }
+            },
+            "required": [
+              "choice",
+              "values"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Asked only when that earlier choice holds one of these values."
+      }
+    },
+    "required": [
+      "key",
+      "label",
+      "help",
+      "options",
+      "max_picks",
+      "shown_when"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / recipe / properties / recipe / properties / id
```
Added value: +{
+  "format": "uuid",
+  "type": "string"
+}
```

addedOutput schema / properties / recipe / properties / recipe / properties / inputs

Added value: +{
+  "description": "The media an `arm` or `reprompt` recipe takes, by key.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "help": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "key": {
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "max_items": {
+        "type": "integer"
+      },
+      "media": {
+        "description": "\"image\", \"video\" or \"audio\".",
+        "type": "string"
+      },
+      "required": {
+        "type": "boolean"
+      },
+      "takes_subject": {
+        "description": "Whether this input takes one of your Subjects as `{ \"type\": \"subject\", \"subject_id\" }`.",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "key",
+      "label",
+      "help",
+      "media",
+      "required",
+      "max_items",
+      "takes_subject"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / recipe / properties / recipe / properties / model

Added value: +{
+  "description": "The default model; null on a `run` recipe, whose steps choose their own.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

removedOutput schema / properties / recipe / properties / recipe / properties / model_id
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / recipe / properties / recipe / properties / model_kind

Removed value: -{
-  "enum": [
-    "image",
-    "video",
-    "tts",
-    "music"
-  ],
-  "type": "string"
-}

addedOutput schema / properties / recipe / properties / recipe / properties / object
```
Added value: +{
+  "const": "recipe",
+  "type": "string"
+}
```

addedOutput schema / properties / recipe / properties / recipe / properties / prompt

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "label": {
+          "type": "string"
+        },
+        "max_length": {
+          "type": "integer"
+        },
+        "placeholder": {
+          "type": "string"
+        },
+        "required": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "label",
+        "placeholder",
+        "required",
+        "max_length"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "What `prompt` asks for when you run it; null when it asks for none."
+}

removedOutput schema / properties / recipe / properties / recipe / properties / recipe_id
```
Removed value: -{
-  "format": "uuid",
-  "type": "string"
-}
```
removedOutput schema / properties / recipe / properties / recipe / properties / recommended_model
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```

addedOutput schema / properties / recipe / properties / recipe / properties / recommended_models

Added value: +{
+  "description": "Models its author tested. Any model of its medium that can take its inputs runs it too.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / recipe / properties / recipe / properties / run_inputs / description
```
Added value: +"What a `run` recipe takes, by key; empty on the others."
```
addedOutput schema / properties / recipe / properties / recipe / properties / run_inputs / items / additionalProperties
```
Added value: +true
```

addedOutput schema / properties / recipe / properties / recipe / properties / run_inputs / items / properties

Added value: +{
+  "key": {
+    "type": "string"
+  },
+  "label": {
+    "type": "string"
+  },
+  "type": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / recipe / properties / recipe / properties / run_inputs / items / required
```
Added value: +[
+  "type",
+  "key",
+  "label"
+]
```
addedOutput schema / properties / recipe / properties / recipe / properties / run_inputs / items / type
```
Added value: +"object"
```

addedOutput schema / properties / recipe / properties / recipe / properties / type

Added value: +{
+  "description": "What it makes. New values may be added.",
+  "enum": [
+    "image",
+    "clip",
+    "voiceover",
+    "music"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / recipe / properties / recipe / properties / uses / type
```
Previous value: -"number"New value: +"integer"
```

changedOutput schema / properties / recipe / properties / recipe / required

Previous value: -[
-  "recipe_id",
-  "model_kind",
-  "action",
-  "name",
-  "description",
-  "visibility",
-  "featured",
-  "tags",
-  "uses",
-  "cover_url",
-  "app_url"
-]New value: +[
+  "object",
+  "id",
+  "name",
+  "description",
+  "action",
+  "type",
+  "model",
+  "recommended_models",
+  "prompt",
+  "inputs",
+  "choices",
+  "run_inputs",
+  "tags",
+  "uses",
+  "cover_url",
+  "app_url",
+  "visibility",
+  "featured"
+]

First observedOct 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the mutation hazard of update_recipe's whole-field replacement, the curator-restriction signal, and the notable fact that a run row's `definition` saved as JSON is a workflow file Kuro Desktop can open.

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

Conciseness3/5

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

Front-loaded with the verb and resource, and no sentence is filler. However, the core payload is packed into one long em-dash-laden sentence dense with undefined internal jargon ("arm row," "reprompt row," "doctrine"), which slows parsing more than the information density justifies.

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

Completeness4/5

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

An output schema exists, so return values need not be spelled out, and annotations cover the read-only profile; the description adds the conceptual shape of the response instead. The main gap is that the row-type vocabulary ("arm row," "reprompt row," "run row," "doctrine") is never defined, so an agent may not know how to interpret the returned payload.

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?

Schema description coverage is 0% for the single `recipe_id` parameter, so the description must carry the meaning. It implies the id refers to a recipe the caller owns (across arm/reprompt/run rows) but never states the format, whether it is the same id used by `update_recipe`, or how a public-versus-owned id would behave.

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

Purpose5/5

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

States a specific verb and resource ("Read one recipe you own, whole") and immediately enumerates what is returned across the three row variants — `config` on an arm row, `writer` on a reprompt row, `definition` on a run row — plus catalog submission state, curator restriction, and public page. This distinguishes it from the sibling `get_recipe`, which lacks the ownership framing.

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

Usage Guidelines4/5

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

Gives explicit sequencing guidance: "Use this before update_recipe — a patch replaces `config`, `writer` or `definition` whole," which tells the agent why it must read first. It does not explicitly contrast against `get_recipe` or `list_own_recipes`, leaving alternative selection to inference from the name.

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

All Kuro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?