Oviond

List team members

list_users

Read-only

List all team members on the account

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number (0-indexed)
`limit`	No	Results per page

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	One row per team member — id, email, fullname, role, avatar_url, the clients they can reach, and invite_pending while they have not accepted yet.
`meta`	No	Pagination for the list — page, limit and the total row count.
`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": "One row per team member — id, email, fullname, role, avatar_url, the clients they can reach, and invite_pending while they have not accepted yet.",
+      "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"
+}

First observedSep 18, 2026

TDQS

A3.6/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, covering the safety profile. The description adds the scope detail 'all team members on the account', which clarifies coverage but does not mention pagination behavior or ordering. Given annotation coverage, this adds some value but is not rich, so a 3 is appropriate.

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?

A single factual sentence with zero filler. The purpose and scope are front-loaded and immediately clear, making it easy for an agent to parse quickly.

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 simple 0-required-parameter read-only list operation with an output schema and annotations covering safety, the description is nearly complete. Pagination details are in the schema, and nothing essential for correct invocation is missing. It could mention default page size or that pagination is used, but this is minor.

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%, fully documenting 'page' and 'limit'. The description's word 'all' hints at the operation's scope but doesn't add meaning beyond the schema. Baseline 3 is correct since the schema does the heavy lifting for parameters.

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 uses a specific verb 'List' with the resource 'team members' and scope 'on the account'. This clearly distinguishes it from sibling list tools like list_clients and list_reports, which target different entities. An agent can immediately know what this tool does without opening the schema.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this is for account staff (team members) rather than clients, nor does it route to other user-related tools like get_current_user or invite_user. The agent must infer usage from the resource name alone.

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?