Skip to main content
Glama

Oviond

by com.oviond.api
OverviewDiscussionsAdmin

List activity log

list_activity
Read-only

List the account activity / audit log (who changed what), paginated and filterable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (0-indexed)
limitNoResults per page
searchNoFree-text search
sourceNoFilter by origin: app, api, mcp or system
resource_typeNoFilter by resource type (e.g. client, project, goal)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoOne entry per logged action, newest first — id, action, resource_type, resource_name, the user who made it, the source it came from (app, api, mcp, system) and created_at.
metaNoPagination for the list — page, limit and the total row count.
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": "One entry per logged action, newest first — id, action, resource_type, resource_name, the user who made it, the source it came from (app, api, mcp, system) and created_at.",
+      "items": {},
+      "type": "array"
+    },
+    "meta": {
+      "additionalProperties": true,
+      "description": "Pagination for the list — page, limit and the total row count.",
+      "properties": {
+        "limit": {
+          "description": "Maximum rows per page.",
+          "type": "number"
+        },
+        "page": {
+          "description": "Zero-based index of the page returned.",
+          "type": "number"
+        },
+        "total": {
+          "description": "Total rows matching the query across all pages.",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "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.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, establishing a safe read-only operation. The description adds 'paginated and filterable' as behavioral traits beyond the annotations, and 'who changed what' gives a sense of the content. No side effects or contradictions are present, so it meets the lowered bar with mild additional context.

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?

One sentence, front-loaded with the verb and resource, then the content clarification and capabilities. Every word contributes to understanding; there is no redundancy or filler.

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 read-only list tool with 100% schema coverage, an output schema, and full annotations, the description is complete enough. It tells the agent what the tool does, its content, and its core capabilities. Nothing an agent needs 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so page, limit, search, source, and resource_type are all documented in the schema. The description's mention of 'paginated and filterable' loosely aligns with the parameters but adds no specific semantic detail beyond the schema. Baseline 3 applies.

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 'List', the resource 'account activity / audit log', and clarifies the content with 'who changed what'. This distinguishes it from sibling list tools like list_assets or list_reports, which list different resources. The qualifiers 'paginated and filterable' further set expectations without ambiguity.

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 provides clear context: use this tool to list account activity/audit log entries. The phrase 'who changed what' implies the use case of tracking changes. It doesn't explicitly name alternatives or exclusion scenarios, but the uniqueness of an audit log tool among the siblings makes when-to-use clear enough.

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