Skip to main content
Glama

Oviond

by com.oviond.api
OverviewDiscussionsAdmin

Create client with report

create_client_with_report

Create a new client and its first report or dashboard in one step. The first report is resolved from the inputs: template_id clones that template; blank:true creates an empty report; with neither, a matching Starter template of the given type is cloned (never a blank report). For a specific style (e.g. a Google Ads dashboard), pass a template_id found via list_templates (filter by datasources + type).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesClient name
typeYesReport type: REPORT (point-in-time) or DASHBOARD (live)
blankNoSet true for an empty report. If false/omitted and no template_id is given, a matching Starter template is cloned.
websiteNoClient website, e.g. acme.com
timezoneNoIANA timezone for the client (default UTC)
report_nameYesName for the first report
template_idNoClone this template into the first report (from list_templates — filter by datasources + type)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoWhat was created — the new client and the new report, each with its id and name, and the template the report came from. Link a datasource to the client next, or the widgets show demo data.
successYesTrue when the call succeeded. A failure comes back as an error result instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "What was created — the new client and the new report, each with its id and name, and the template the report came from. Link a datasource to the client next, or the widgets show demo data."
+    },
+    "success": {
+      "description": "True when the call succeeded. A failure comes back as an error result instead.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes beyond annotations by explaining the resolution precedence and the important warning that omitting both options never creates a blank report. The only minor gap is the lack of an explicit precedence statement when both template_id and blank:true are supplied together.

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, no filler, and the key behavior is front-loaded. Every sentence earns its place by adding resolution logic or practical guidance.

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 composite creation tool, the description covers the decision branches, warns against unintended blank reports, and points to the right template search path. With an output schema present, return details are not required; only the combined-option ambiguity keeps this from being fully complete.

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?

Schema coverage is 100%, so the baseline is 3; the description adds meaningful semantics for template_id, blank, and type, including the list_templates filtering hint. It does not add new meaning for name/report_name/website/timezone, but those are already described in the schema.

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 action and resources: 'Create a new client and its first report or dashboard in one step.' It clearly differentiates from siblings like create_client and create_report by emphasizing the one-step combined behavior.

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?

Provides clear conditional guidance: use template_id to clone, blank:true for empty, and neither to clone a matching Starter template. It also directs users to list_templates for specific styles. However, it does not explicitly state when to prefer separate create_client/create_report calls instead.

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