Oviond

Archive multiple reports

archive_reports

Destructive

Archive several reports by ID in one call. They go to the archive, not away — list_archive shows them and restore_from_archive brings them back.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	Yes	Array of report IDs to archive (from list_reports)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	Confirmation of the archive and how many reports it covered.
`success`	Yes	True when the call succeeded. A failure comes back as an error result instead.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Confirmation of the archive and how many reports it covered."
+    },
+    "success": {
+      "description": "True when the call succeeded. A failure comes back as an error result instead.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedSep 18, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already indicate destructiveHint=true, and the description adds valuable nuance by clarifying that archiving is reversible and not permanent ('not away', 'restore_from_archive brings them back'). This goes beyond the annotation to disclose the non-destructive nature in practice, which is critical for an agent to assess risk.

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 concise sentences: the first states the core action, the second clarifies the outcome and points to related tools. No redundant words, front-loaded purpose, and efficient structure.

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 simple single-parameter tool with an output schema and annotations, the description covers purpose, scope, and reversibility. It also references the archive lifecycle via sibling tools. Nothing an agent needs to decide whether to call it or interpret results 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 coverage is 100%, so the parameter 'ids' is fully described as an array of report IDs. The tool description adds no additional meaning beyond the schema's own description, which already mentions 'from list_reports'. Baseline 3 is appropriate because the schema handles the semantics and the description does not compensate further.

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 verb (archive), resource (reports), and scope (several by ID in one call). It explicitly differentiates from the sibling archive_report by emphasizing batch operation. The phrase 'They go to the archive, not away' clarifies the semantic outcome, making it 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?

The description implies usage for multiple reports via 'several' and 'in one call', which contrasts with the singular archive_report sibling. However, it does not explicitly state 'use archive_report for a single report' or provide exclusion conditions. It gives lifecycle context (list_archive, restore_from_archive) but lacks explicit when/when-not guidance.

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?