Oviond

Move widget

move_widget

Move or resize a widget. Works for any widget type. Pass only the dimensions you want to change.

Input Schema

TableJSON Schema

Name	Required	Description
`x`	No	New x position (grid column 0-11).
`y`	No	New y position (grid row).
`id`	Yes	Widget ID (from list_widgets).
`width`	No	New width in grid columns.
`height`	No	New height in grid rows.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	The widget, at its new position and size, as saved, with the update applied.
`success`	Yes	True when the call succeeded. A failure comes back as an error result instead.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "The widget, at its new position and size, as saved, with the update applied.",
+      "type": "object"
+    },
+    "success": {
+      "description": "True when the call succeeded. A failure comes back as an error result instead.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedSep 18, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive mutation. The description adds useful partial-update context, but it does not go further to disclose validation behavior, failure modes, or how other properties are preserved.

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

Conciseness5/5

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

The description is three short sentences with no filler. Purpose, applicability, and usage guidance are all front-loaded, and each sentence contributes value.

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?

The schema fully documents parameters and required fields, and an output schema exists, so the description does not need to repeat return details. The main omission is explicit guidance on when to choose this generic tool over the many per-type update_widget siblings.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds the key semantic that only supplied dimensions are changed. This is genuinely useful beyond the schema, though 'dimensions' is slightly ambiguous with respect to x/y position versus width/height.

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 description clearly states the action ('Move or resize a widget') and notes it works for any widget type, so an agent can understand the tool's scope. It does not explicitly name sibling tools like update_*_widget, so it stops short of the highest differentiation bar.

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?

It gives practical guidance: pass only the dimensions you want to change, which clarifies partial updates and how to use the tool. It does not explicitly say when to prefer a type-specific update_*_widget instead, so it lacks full when-not/alternative guidance.

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

All Oviond 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?