Skip to main content
Glama

oviond

by com.oviond
OverviewDiscussionsAdmin

Update text widget

update_text_widget

Update a TEXT widget — an executive summary, commentary, any prose block. The body accepts Markdown. Replaces the entire text content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesBody text. Markdown is rendered: # / ## / ### headings, - and 1. lists, **bold**, *italic*, ~~strike~~, `code`, > quotes, ``` fences and [links](url). Plain prose works too — it becomes paragraphs. Replaces the existing content entirely.
widget_idYesWidget ID (from list_widgets).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoThe text widget as saved, with the update applied.
successYesTrue when the call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 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"
-}
    • changedInput schema / properties / text / description
      Previous value: -"New plain-text content. Replaces existing."New value: +"Body text. Markdown is rendered: # / ## / ### headings, - and 1. lists, **bold**, *italic*, ~~strike~~, `code`, > quotes, ``` fences and [links](url). Plain prose works too — it becomes paragraphs. Replaces the existing content entirely."
    • addedInput schema / properties / widget_id
      Added value: +{
+  "description": "Widget ID (from list_widgets).",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "text"
-]New value: +[
+  "widget_id",
+  "text"
+]
    • 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.3/5.0
Behavior4/5

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

The description explicitly discloses the key behavioral trait: 'Replaces the entire text content,' preventing an agent from assuming an append or partial edit. It also notes Markdown support. Annotations already indicate this is a mutation, and the description adds the meaningful replacement nuance without contradicting them.

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, focused sentences with no filler. The resource type and core behavior are front-loaded, and every sentence adds useful context.

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?

For a two-parameter update tool with a rich input schema, an output schema, and clear sibling differentiation, the description covers the purpose, the content type, Markdown support, and replacement semantics. Nothing essential for invoking the tool 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%, and the schema already documents both parameters in detail, including the Markdown syntax and the full-replacement behavior. The tool description adds no new parameter-specific meaning beyond what the schema provides, so the baseline of 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 action ('Update') and the resource ('TEXT widget'), and further defines what a text widget is: an executive summary, commentary, or prose block. This distinguishes it from sibling update_*_widget tools by emphasizing prose 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?

The description gives a clear usage context: use this for text/prose widgets whose body accepts Markdown. It does not explicitly name alternative tools or provide when-not-to-use guidance, but the resource type is well-enough scoped to make the intended use obvious among the siblings.

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