Skip to main content
Glama

oviond

by com.oviond
OverviewDiscussionsAdmin

Update static value widget

update_static_value_widget

Set the value on a Static Value widget — a number, an amount like "R50", or free text like "Active". It has no datasource and never fetches, so the value is shown exactly as passed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoLabel shown above the value.
valueYesThe value to display.
widget_idYesWidget ID (from list_widgets).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoThe widget as saved, holding the value inline. Nothing is fetched, so it is already showing what you passed.
successYesTrue when the call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • 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",
-  "value"
-]New value: +[
+  "widget_id",
+  "value"
+]
    • 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."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses key behavioral traits: the widget has no datasource and never fetches, so the value is shown exactly as passed. This goes beyond the annotations (readOnlyHint=false, destructiveHint=false) by explaining the widget's data behavior. It doesn't mention side effects or permissions, but the annotations already cover the safety profile.

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 sentences with zero waste. The core action is front-loaded, examples clarify the value format, and the behavioral note about no datasource is concise and valuable.

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 description is complete for a simple update tool. It explains the value semantics and the widget's behavior. The output schema exists, so return values are covered. It could mention that widget_id comes from list_widgets, but the schema already says that.

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 schema already documents all three parameters. The description adds context about the value parameter (examples like 'R50' or 'Active') but doesn't add meaning beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the tool's purpose: 'Set the value on a Static Value widget' with specific examples of value types. It distinguishes this from other update_*_widget tools by emphasizing the static value widget's unique behavior (no datasource, never fetches).

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 implies when to use this tool: when updating a Static Value widget, as opposed to other widget types. It doesn't explicitly name alternatives or exclusions, but the context of sibling tools (update_data_widget, update_calculated_metric_widget, etc.) makes the usage context clear.

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

All oviond toolsInspect
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