Skip to main content
Glama

oviond

by com.oviond
OverviewDiscussionsAdmin

Audit report health

audit_report_health
Read-only

Audit a report or dashboard: list its connected data sources and automation state, and flag likely issues (no data sources connected, paused automations). Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
report_idYesReport ID to audit (from list_reports)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoThe audit — the report, the datasources its client has connected, its automations and their state, and the issues found (no datasource connected, automations paused).
successYesTrue when the call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / id
      Removed value: -{
-  "description": "Report ID to audit (from list_reports)",
-  "type": "string"
-}
    • addedInput schema / properties / report_id
      Added value: +{
+  "description": "Report ID to audit (from list_reports)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "id"
-]New value: +[
+  "report_id"
+]
    • 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?

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Read-only.' It goes beyond the annotations by explaining what the audit covers: connected data sources, automation state, and specific issue types like no data sources or paused automations.

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 two sentences, front-loads the core action, and every clause adds information about what the tool does or does not do. The 'Read-only.' tag is compact and reinforces the safety profile without padding.

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 single-parameter, read-only tool with an output schema, the description is complete: it states the input expectation implicitly through the schema, describes what the audit includes, and warns about read-only behavior. There are no missing concepts an agent would need to invoke it correctly.

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% for the single parameter, and the schema description 'Report ID to audit (from list_reports)' is already informative. The description adds no additional parameter-level meaning, so it meets the baseline but does not exceed it.

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 names a specific action ('Audit'), the resource ('report or dashboard'), and the concrete outputs: connected data sources, automation state, and likely issues. This clearly distinguishes it from sibling tools like connected_datasources or list_automations, which only cover part of this functionality.

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 phrase 'Audit a report or dashboard' plus 'flag likely issues' gives clear context for when to use this tool: as a health check rather than a raw data retrieval. It does not explicitly name alternative tools or exclusion cases, so it falls just short of full guidance.

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