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).
`width`	No	New width in grid columns.
`height`	No	New height in grid rows.
`widget_id`	Yes	Widget ID (from list_widgets).

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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 25, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / properties / id

Removed value: -{
-  "description": "Widget ID (from list_widgets).",
-  "type": "string"
-}

addedInput schema / properties / widget_id

Added value: +{
+  "description": "Widget ID (from list_widgets).",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "id"
-]New value: +[
+  "widget_id"
+]

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedOutput schema / properties / success / description

Previous value: -"True when the call succeeded. A failure comes back as an error result instead."New value: +"True when the call succeeded."

First observedSep 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the mutating yet non-destructive nature is already structured. The description adds valuable behavioral context: it works for any widget type and that omitted dimensions are left unchanged (partial updates), which annotations do not convey.

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?

Two short sentences, front-loaded with the primary action, and no filler. Every clause adds relevant guidance.

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?

For a simple mutation tool with full schema coverage and an output schema, the description covers purpose, scope, and partial-update behavior. It does not mention error handling or exact return, but those are adequately covered by the schema and output schema.

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 coverage is 100% and each parameter has a description. The description adds semantic value beyond the schema by stating 'Pass only the dimensions you want to change,' which clarifies that optional parameters are not all required but selectively applied.

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?

The description states a specific verb and resource ('Move or resize a widget'), scopes it with 'Works for any widget type', and implies a partial-update behavior via 'Pass only the dimensions you want to change.' This clearly distinguishes it from sibling update_*_widget tools that modify content.

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 conveys when to use the tool (repositioning/resizing an existing widget regardless of type) and how to use it ('Pass only the dimensions you want to change'). It does not explicitly name alternatives or provide when-not-to-use guidance, but the context is clear enough.

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?