Hovercode

list_folders

Read-onlyIdempotent

List the workspace's folders with their full path, code count, id and slug. Use a folder's id or slug with create_qr_code / update_qr_code (folder) to file codes, or with list_qr_codes to filter.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_folders"
  }
}

Input Schema

Name	Required	Description	Default
`workspace`	No	Workspace id. Optional when the account has one workspace; use list_workspaces to resolve otherwise.

Output Schema

Name	Required	Description
`next`	No	URL of the next page, or null on the last page.
`count`	No	Total matching rows across all pages.
`error`	No	Present only when the tool failed (isError): cause, retryable, message.
`results`	No
`previous`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 13, 2026

removedOutput schema / properties / error / additionalProperties
```
Removed value: -true
```

changedOutput schema / properties / error / description

Previous value: -"Present only when the tool failed (the result is also flagged isError)."New value: +"Present only when the tool failed (isError): cause, retryable, message."

removedOutput schema / properties / error / properties

Removed value: -{
-  "cause": {
-    "description": "Machine-readable failure category: invalid_argument, not_found, forbidden, plan_limit, rate_limited, or server_error.",
-    "type": "string"
-  },
-  "message": {
-    "type": "string"
-  },
-  "retryable": {
-    "description": "Whether repeating the same call could succeed.",
-    "type": "boolean"
-  }
-}

removedOutput schema / properties / results / items

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "code_count": {
-      "type": "integer"
-    },
-    "created": {
-      "type": "string"
-    },
-    "id": {
-      "type": "string"
-    },
-    "name": {
-      "type": "string"
-    },
-    "parent": {
-      "description": "Parent folder id, null at the top level.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "path": {
-      "description": "Full path, e.g. Campaigns / Spring 2026.",
-      "type": "string"
-    },
-    "slug": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "description": "Total matching rows across all pages.",
+      "type": "integer"
+    },
+    "error": {
+      "additionalProperties": true,
+      "description": "Present only when the tool failed (the result is also flagged isError).",
+      "properties": {
+        "cause": {
+          "description": "Machine-readable failure category: invalid_argument, not_found, forbidden, plan_limit, rate_limited, or server_error.",
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retryable": {
+          "description": "Whether repeating the same call could succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "next": {
+      "description": "URL of the next page, or null on the last page.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "previous": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "code_count": {
+            "type": "integer"
+          },
+          "created": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "parent": {
+            "description": "Parent folder id, null at the top level.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "path": {
+            "description": "Full path, e.g. Campaigns / Spring 2026.",
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds the scope (workspace-scoped folders) and the returned fields, but nothing about limits, pagination or ordering; with the annotation bar lowered, this is adequate but thin.

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 tight sentences, zero filler, with the core purpose and return shape front-loaded before the downstream-usage routing.

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 zero-required-parameter, read-only list tool with an output schema and full annotation coverage, the description supplies purpose plus next-step routing. Return values are already covered by the output schema, so nothing essential is missing, though pagination/ordering behavior is left unstated.

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 coverage is 100% and the single optional 'workspace' parameter is fully documented in the schema, so the baseline is 3. The description only indirectly references the workspace scope and adds no syntax or fallback detail beyond 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?

States a specific verb and resource ('List the workspace's folders') and enumerates exactly what each item returns (full path, code count, id, slug). An agent can immediately distinguish this read tool from the sibling create_folder/update_folder/delete_folder.

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?

Explicitly tells the agent what to do with the ids/slugs it returns, naming create_qr_code, update_qr_code and list_qr_codes as the consumers. It does not, however, state when to prefer this over list_workspaces or otherwise bound the call context, so it stops short of full alternatives/exclusions coverage.

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

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