Cleotic

List reports

list_reports

Read-onlyIdempotent

The brand's saved reports, with their date ranges and public share links. Use it to find a report to revoke_report; create_report makes a new one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`brand`	Yes	Brand or study: its ID from list_brands, or its name (exact or a unique prefix).

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes
`generated_at`	Yes	RFC 3339 time the response was made.
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 1, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / brand / minLength
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": false,
+      "properties": {
+        "brand": {
+          "additionalProperties": false,
+          "properties": {
+            "id": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "url": {
+              "description": "The brand's website, or empty when none is set.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "url"
+          ],
+          "type": "object"
+        },
+        "reports": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "created_at": {
+                "type": "string"
+              },
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "period": {
+                "additionalProperties": false,
+                "properties": {
+                  "from": {
+                    "description": "First day, YYYY-MM-DD.",
+                    "type": "string"
+                  },
+                  "to": {
+                    "description": "Last day, YYYY-MM-DD.",
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "from",
+                  "to"
+                ],
+                "type": "object"
+              },
+              "public_url": {
+                "description": "Anyone with this link can read the report; empty when revoked.",
+                "type": "string"
+              },
+              "revoked": {
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "id",
+              "name",
+              "period",
+              "created_at",
+              "public_url",
+              "revoked"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "brand",
+        "reports"
+      ],
+      "type": "object"
+    },
+    "generated_at": {
+      "description": "RFC 3339 time the response was made.",
+      "type": "string"
+    },
+    "schema_version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema_version",
+    "generated_at",
+    "data"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedSep 30, 2026

addedInput schema / properties / brand

Added value: +{
+  "description": "Brand or study: its ID from list_brands, or its name (exact or a unique prefix).",
+  "type": "string"
+}

removedInput schema / properties / project_id

Removed value: -{
-  "description": "Cleotic project ID.",
-  "type": "string"
-}

removedInput schema / properties / project_name

Removed value: -{
-  "description": "Project name. Exact case-insensitive names and unique prefixes are supported.",
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "brand"
+]
```

First observedSep 30, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered by structured data. The description adds return-content context (date ranges, share links) but says nothing about pagination, result volume, or rate limits, so it is only modestly additive.

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 compact sentences, zero filler, with the inventory of the resource front-loaded before the routing guidance for related tools.

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?

Output schema exists, so return values need no explanation, and annotations cover the safety profile. The description is essentially complete for a simple one-param list tool, with only pagination/result-size behavior unaddressed.

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?

One parameter with 100% schema description coverage; the schema already explains that brand accepts an ID from list_brands or an exact/unique-prefix name. The description adds no format or syntax detail beyond that, so the baseline 3 is warranted.

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?

States the specific resource ('the brand's saved reports') and its scope, plus what the listing carries (date ranges, public share links). It explicitly differentiates from both revoke_report and create_report, so an agent can place it among siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives a concrete when-to-use condition ('find a report to revoke_report') and routes the create case to create_report. The alternative tools and the condition selecting each are named rather than left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cleotic 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?