oviond

Create theme

create_theme

Create a new visual theme. Supply the complete tokens map (primary, font, radius, shadow, canvas, surface, chart1-10, etc.) — tokens are the single source of truth for every visual property. A theme also picks the report cover-page and thank-you-page background images (other text/colour overlays come from defaults). Set is_default=true to make this the account default — any existing default is cleared atomically.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Theme name
`tokens`	Yes	Complete token map for all visual properties: primary, primary_foreground, accent, accent_foreground, canvas, surface, surface_muted, text, text_muted, border, header_surface, header_text, header_border, chart1–chart10, font, radius, shadow.
`cover_page`	No	Cover-page configuration: background image URL plus title and subtitle overlays (variable-substituted at render time).
`is_default`	No	Mark as the account default theme — one per account, cascade target for new reports
`thank_you_page`	No	Thank-you-page configuration: background image + title + subtitle.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	The new theme — id, name, tokens and page config. Pass the id as theme_id on a report.
`success`	Yes	True when the call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 25, 2026

removedInput schema / $schema

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

removedInput schema / properties / cover_page / properties / widgets
```
Removed value: -{
-  "items": {},
-  "type": "array"
-}
```
removedInput schema / properties / thank_you_page / properties / widgets
```
Removed value: -{
-  "items": {},
-  "type": "array"
-}
```

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/5.0

Behavior4/5

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

Annotations already signal a write operation (readOnlyHint=false) that is not destructive. The description adds genuinely useful behavior beyond that: tokens are the 'single source of truth for every visual property,' overlays come from defaults, and setting is_default=true clears any existing default 'atomically.' This side-effect disclosure is exactly the kind of context annotations cannot provide.

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?

Three sentences, roughly 75 words, with the core purpose front-loaded. Each sentence earns its place: the tokens requirement, the cover/thank-you page behavior, and the is_default side effect. No filler, no repetition of schema content.

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 tool with 5 parameters and two nested objects, the description plus the rich 100%-covered schema and existing output schema provide enough for correct invocation. The description covers the key behavioral nuances (complete tokens, default clearing, overlay defaults). A minor gap is that it doesn't explicitly note cover_page/thank_you_page are optional, though the schema's required list already conveys 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 baseline is 3. The description reinforces the completeness requirement for tokens and adds the atomic default-clearing nuance for is_default, but the schema already documents each parameter thoroughly (including the full token list and the 'one per account' default semantics). The added value over the schema is marginal.

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 opening sentence 'Create a new visual theme' states a specific verb and resource, and the rest of the description clarifies what a theme is (tokens map, cover/thank-you page images, default flag). This clearly distinguishes it from siblings like update_theme, get_theme, list_themes, and archive_theme, which are all different operations on the same resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage — create a new theme when you need a fresh visual theme and supply the complete tokens map. However, it never explicitly names alternatives or exclusions, such as 'use update_theme to modify an existing theme' or 'use get_theme to inspect current settings.' Given the large sibling list, explicit routing would meaningfully help 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 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?