oviond

Change report date range

change_report_date_range

Set the period a report covers. Every data widget on it is re-fetched for the new range and the results are saved — widgets on their own custom range keep it. A rolling preset ("Last 30 Days") is stored as the preset and re-resolved on every later fetch, so it stays current. The re-fetch runs in the background — call get_widget_data with source_id set to this report to read the new numbers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`report_id`	Yes	Report ID (from list_reports)
`date_range`	Yes	The period to report on

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	The report carrying the new date_range. Every data widget on it is re-fetching in the background — read the new numbers with get_widget_data.
`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": "Report ID (from list_reports)",
-  "type": "string"
-}

addedInput schema / properties / report_id

Added value: +{
+  "description": "Report ID (from list_reports)",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "id",
-  "date_range"
-]New value: +[
+  "report_id",
+  "date_range"
+]

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

Behavior5/5

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

The description discloses substantial behavior beyond the annotations: widgets are re-fetched and saved, widgets on custom ranges keep them, rolling presets are stored and re-resolved, and the re-fetch is background. This adds rich context that the annotations (readOnlyHint false, destructiveHint false) do not 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 with no wasted words. The main action is front-loaded, and each sentence adds essential behavioral detail without bloat.

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 tool with a nested date_range object and an output schema, the description covers the key usage context: effect on widgets, background re-fetch, and how to retrieve results. Nothing needed to call it correctly is missing.

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?

The schema already documents all parameters with 100% coverage, so the baseline is 3. The description adds meaning by explaining how the date_range object behaves (rolling presets, custom range preservation), which complements the schema without redundancy.

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 the specific verb 'Set' and the resource 'period a report covers', and goes further to explain the re-fetch and saving behavior, which clearly distinguishes it from update_report and other tools. The purpose is unambiguous.

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 clearly describes when to use the tool (to change a report's date range) and even directs the agent to call get_widget_data to read results. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls short of a 5.

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?