Vidova

List projects

list_projects

Read-onlyIdempotent

List the signed-in account's Vidova projects, newest first, a page at a time, and the id of the open one. query finds projects by words of their name. The answer gives total and nextOffset: pass nextOffset as offset for the next page; null means this page is the last.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "offset": "<offset>",
      "limit": "<limit>"
    },
    "name": "list_projects"
  }
}

Input Schema

Name	Required	Description
`limit`	Yes	Most projects on the page, 1 to 100. null means 30.
`query`	Yes	Words in the project's name, for example dr pepper. Every word must appear. null or empty lists every project.
`offset`	Yes	Projects to skip: the nextOffset of the page before. null starts at the newest.

Output Schema

Name	Required	Description	Default
`activeId`	Yes
`projects`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 22, 2026

addedInput schema / properties / limit

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Most projects on the page, 1 to 100. null means 30."
+}

addedInput schema / properties / offset

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Projects to skip: the nextOffset of the page before. null starts at the newest."
+}

addedInput schema / properties / query

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Words in the project's name, for example dr pepper. Every word must appear. null or empty lists every project."
+}

addedInput schema / required

Added value: +[
+  "query",
+  "offset",
+  "limit"
+]

First observedOct 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine context beyond that: deterministic newest-first ordering, per-account scope, and the pagination contract (total/nextOffset, null = last page).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences, front-loaded with the core action and scope, then pagination. Slightly dense mixing of return-shape and paging instructions, but no filler.

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 are partly covered, yet the description still clarifies total/nextOffset pagination meaningfully. Annotations handle safety; remaining detail is largely complete for a simple list tool.

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?

With 100% schema description coverage, baseline is 3, but the description adds cross-parameter linkage the schema lacks: passing nextOffset as offset for the following page, and query matching words of the name. This raises it above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list Vidova projects), scopes it to the signed-in account, and adds ordering (newest first). It stops short of explicitly distinguishing itself from siblings like get_active_project or open_project, even though it mentions returning 'the id of the open one'.

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

Usage Guidelines3/5

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

Explains how to use query to find projects by name and how to page via offset, which implies the usage context. But it never names an alternative or states when a different tool (e.g. get_active_project, search) should be preferred.

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

All Vidova 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.