Wiro MCP Server

Official

by wiroai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Get a Wiro model schema

get_model_schema

Read-onlyIdempotent

Retrieve a model's typed parameters, required fields, defaults, options, and pricing to fill valid run requests and answer price questions.

Instructions

Get one model’s typed parameters, options, defaults, required fields, and pricing. Catalog fields such as session_id and previousTaskToken must be discovered here: a chat continues with the same session_id and the next prompt, and previousTaskToken with toolOutputs continues a turn that ended with tool calls. Fill required parameters and follow the returned run_model next action once when the user wants a run; for a price question, the price here is the answer. A price set when the run ends, or turn by turn in a live session, gives the rates, and the charge is known after the run. "No fixed price" means the run is charged for the time it takes. It also describes the built-in workflow utilities (workflow-utilities/output-filter, workflow-utilities/merge-text, workflow-utilities/split-text): their parameters and the output ports other workflow steps reference.

Input Schema

Name	Required	Description	Default
`model`	Yes	Model slug in "owner/model" format, e.g. "google/veo3-1", "black-forest-labs/flux-2-pro", or a workflow utility such as "workflow-utilities/output-filter".

Output Schema

Name	Required	Description	Default
`model`	Yes
`nextAction`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.4.1Nov 1, 2026

changedInput schema / properties / model / description

Previous value: -"Model slug in \"owner/model\" format, e.g. \"openai/sora-2\", \"black-forest-labs/flux-2-pro\"."New value: +"Model slug in \"owner/model\" format, e.g. \"google/veo3-1\", \"black-forest-labs/flux-2-pro\", or a workflow utility such as \"workflow-utilities/output-filter\"."

addedOutput schema / properties / model / properties / discountPercent

Added value: +{
+  "description": "Your discount on this model, in percent. It comes off the part of a charge paid from deposits; coupon credit and store revenue pay first, at the list price in pricing.",
+  "type": "number"
+}

addedOutput schema / properties / model / properties / dynamicOutputs
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / model / properties / estimatedCostUsd / description

Added value: +"Estimated USD cost of one run: the average of past runs for a model billed by run time, or the listed estimate of a price set when the run ends. Null when there is no such estimate, as for a model priced by its options: see pricing."

addedOutput schema / properties / model / properties / outputs

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "label",
+      "type"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / model / properties / parameters / items / properties / items / items / properties / default / description
```
Added value: +"What a run uses when the parameter is left out."
```

addedOutput schema / properties / model / properties / parameters / items / properties / items / items / properties / sample

Added value: +{
+  "description": "The value from the model's page. A workflow step that leaves the parameter out gets it. A run does not: it leaves an optional parameter empty (a seed is picked at random) and refuses a required one that is left out.",
+  "type": "string"
+}

addedOutput schema / properties / model / properties / pricingNotes

Added value: +{
+  "description": "Notes from the model's price list, as its page shows them, such as the rates behind a price or the setting it applies to.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed3 schema fields changedv1.3.0Aug 29, 2026
- addedOutput schema / properties / model / properties / parameters / items / properties / items / items / properties / advanced
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / model / properties / parameters / items / properties / items / items / properties / jsonSchema
```
Added value: +{
+  "additionalProperties": {},
+  "type": "object"
+}
```
- changedOutput schema / properties / model / properties / parameters / items / properties / items / items / required
```
Previous value: -[
-  "id",
-  "type",
-  "label",
-  "required",
-  "options"
-]New value: +[
+  "id",
+  "type",
+  "label",
+  "required",
+  "options",
+  "advanced"
+]
```

Changed2 schema fields changedv1.2.3Aug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedv1.2.1Aug 2, 2026

changedInput schema / properties / model / description

Previous value: -"Model slug in \"owner/model\" format, e.g. \"openai/sora-2\", \"black-forest-labs/flux-2-pro\""New value: +"Model slug in \"owner/model\" format, e.g. \"openai/sora-2\", \"black-forest-labs/flux-2-pro\"."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "model": {
+      "additionalProperties": false,
+      "properties": {
+        "categories": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "description": {
+          "type": "string"
+        },
+        "estimatedCostUsd": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "parameters": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "items": {
+                "items": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "default": {
+                      "type": "string"
+                    },
+                    "description": {
+                      "type": "string"
+                    },
+                    "id": {
+                      "type": "string"
+                    },
+                    "label": {
+                      "type": "string"
+                    },
+                    "max": {
+                      "type": "number"
+                    },
+                    "min": {
+                      "type": "number"
+                    },
+                    "note": {
+                      "type": "string"
+                    },
+                    "options": {
+                      "items": {
+                        "additionalProperties": false,
+                        "properties": {
+                          "label": {
+                            "type": "string"
+                          },
+                          "value": {
+                            "type": "string"
+                          }
+                        },
+                        "required": [
+                          "label",
+                          "value"
+                        ],
+                        "type": "object"
+                      },
+                      "type": "array"
+                    },
+                    "placeholder": {
+                      "type": "string"
+                    },
+                    "required": {
+                      "type": "boolean"
+                    },
+                    "step": {
+                      "type": "number"
+                    },
+                    "type": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "id",
+                    "type",
+                    "label",
+                    "required",
+                    "options"
+                  ],
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "title": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "title",
+              "items"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "pricing": {
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "slug",
+        "title",
+        "categories",
+        "parameters"
+      ],
+      "type": "object"
+    },
+    "nextAction": {
+      "additionalProperties": false,
+      "properties": {
+        "arguments": {
+          "additionalProperties": {},
+          "type": "object"
+        },
+        "reason": {
+          "type": "string"
+        },
+        "tool": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "tool",
+        "arguments",
+        "reason"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "model",
+    "nextAction"
+  ],
+  "type": "object"
+}

First observedv1.1.4Jun 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds real context on top: that session_id and previousTaskToken are catalog fields only discoverable here, how a chat continues with the same session_id, how previousTaskToken plus toolOutputs resumes a tool-call turn, and how pricing is determined (at run end, per-turn in live sessions, or time-based when 'no fixed price'). That is substantive disclosure beyond the annotations, though the pricing sentence is somewhat opaque.

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?

The purpose is front-loaded, which is good, but the middle pricing passage ('A price set when the run ends, or turn by turn in a live session, gives the rates...') is dense and hard to parse for a one-parameter lookup tool. Chat-continuation semantics, pricing rules, and workflow utilities are packed into a short space without clean separation.

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

Completeness5/5

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

With an output schema and rich annotations already present, the description's job is to cover what they cannot, and it does: where to find session_id/previousTaskToken, how continuation works, the next action to take, and how pricing is reported. Nothing an agent needs in order to call this correctly is missing.

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 100%, so the sole `model` parameter is already fully documented with format and examples. The prose adds little about the parameter itself beyond reiterating that workflow utility slugs are valid inputs, which the schema already shows. Baseline 3 applies when the schema does the heavy lifting.

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 opening sentence is a specific verb+resource: it returns one model's typed parameters, options, defaults, required fields, and pricing, plus later notes it also documents workflow utility schemas. It is clearly not a listing/search tool, though it never names siblings like search_models or recommend_model to draw the contrast explicitly.

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?

The description gives concrete routing: fill required parameters and follow the returned `run_model` next action when the user wants a run, and treat the price shown here as the answer for price questions. It also states that chat-continuation tokens must be sourced here. It stops short of an explicit comparison to search_models/recommend_model, so it is strong but not complete.

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

Deploy Server