Apply2Volunteer

List forms

list_forms

Read-onlyIdempotent

List forms that belong to the authenticated organization. Requires an org API key with the forms:read scope. When a form is published and not soft-deleted, that item also includes publicUrl, publicFormUrl, embedUrl, and embedSnippet, and a draft that was never published omits those fields. A soft-deleted form omits those fields too.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`forms`	Yes	Forms in this organization. The text block is this array as JSON.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 19, 2026

addedOutput schema / properties / forms / items / properties / embedSnippet

Added value: +{
+  "description": "Script tag that embeds the form. Omitted when the form has never been published or is soft-deleted.",
+  "type": "string"
+}

addedOutput schema / properties / forms / items / properties / embedUrl

Added value: +{
+  "description": "Iframe URL, /{org}/{form}?embed=1. Omitted when the form has never been published or is soft-deleted.",
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / forms / items / properties / publicFormUrl

Added value: +{
+  "description": "Canonical public form URL. Omitted when the form has never been published or is soft-deleted.",
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / forms / items / properties / publicUrl

Added value: +{
+  "description": "Same URL as publicFormUrl. Omitted when the form has never been published or is soft-deleted.",
+  "format": "uri",
+  "type": "string"
+}

Changed1 schema field changedOct 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "forms": {
+      "description": "Forms in this organization. The text block is this array as JSON.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "createdAt": {
+            "type": "integer"
+          },
+          "currentVersionId": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "deletedAt": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "id": {
+            "description": "Form id.",
+            "type": "string"
+          },
+          "orgId": {
+            "type": "string"
+          },
+          "settings": {
+            "description": "Client settings JSON. Internal keys are omitted.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": "string"
+          },
+          "status": {
+            "description": "draft or published.",
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "updatedAt": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "id",
+          "orgId",
+          "slug",
+          "title",
+          "status",
+          "currentVersionId",
+          "settings",
+          "createdAt",
+          "updatedAt",
+          "deletedAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "forms"
+  ],
+  "type": "object"
+}

First observedOct 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real context: the required org API key and forms:read scope, plus the state-dependent presence of publicUrl/publicFormUrl/embedUrl/embedSnippet for published vs draft vs soft-deleted forms.

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?

Front-loaded with purpose then auth then field behavior; every sentence carries information. The last two sentences about omitted fields could be merged, but nothing is wasted.

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 parameterless read tool with an output schema, the description supplies everything not already structured: the auth scope and the conditional-field rules that explain why some items look sparser.

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?

The tool takes zero parameters and schema coverage is 100%, so the baseline is 4. There is no parameter syntax the description could usefully add.

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 (List) and resource (forms) and scopes it precisely to 'forms that belong to the authenticated organization,' which separates it from the single-record sibling get_form.

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?

Usage is implied by the org-scoped framing, but the description never says when to pick this over alternatives like get_form or list_applications, nor any exclusions such as archived workspaces. Adequate but leaves routing to inference.

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

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