Skip to main content
Glama

oviond

by com.oviond
OverviewDiscussionsAdmin

Save widgets as a section

create_asset

Save widgets as a reusable section, the same way the editor does when you select widgets and save them: each widget is copied onto the section with a fresh id, and its type and datasources are derived from what you picked. Use add_asset_to_page to drop the section onto a report page later.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSection display name.
tagsNoCategorization tags.
widget_idsYesWidgets to save into the section (ids from list_widgets). Their current config is copied.
descriptionNoSection description.
is_recommendedNoPromote this section to the top of the default "Recommended" sort.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoThe new saved section — id, name and tags. Pass the id to add_asset_to_page to drop it onto a report.
successYesTrue when the call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • 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?

Annotations provide only broad hints (readOnlyHint false, destructiveHint false). The description adds meaningful behavioral detail: each widget is copied with a fresh id, and type/datasources are derived from the selection. This goes beyond the annotations by explaining exactly what happens to the widget configuration, making the tool's behavior predictable.

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 no filler. The first sentence front-loads the action and copy semantics; the second provides a useful pointer to the downstream tool. The editor analogy earns its place by anchoring the behavior in a familiar workflow.

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?

With an output schema present and readOnly/destructive hints provided, the description covers the essential behavior and copy semantics while referencing the next-step tool. It does not discuss permissions or preconditions, but for this complexity level and schema richness it is sufficiently complete for correct invocation.

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 baseline is 3. The description adds minimal extra meaning beyond the schema—'derived from what you picked' loosely echoes the widget_ids parameter, but it doesn't clarify any parameter syntax, constraints, or interactions beyond what the schema already documents.

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: save widgets as a reusable section, and clarifies the behavior with the editor analogy. It also names the complementary sibling add_asset_to_page, distinguishing the creation step from the later placement step. This is unambiguous and sets the tool apart from related siblings like create_template or duplicate_asset.

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 clear context for when to use the tool (to create a reusable section from selected widgets) and explicitly points to add_asset_to_page for the next step. It does not list exclusions or conditions for choosing this over other creation tools, but the context is strong enough to guide an agent.

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