Skip to main content
Glama
Sign In

Apply2Volunteer

by com.applytovolunteer
OverviewDiscussionsAdmin

Read a form preview

get_preview
Read-onlyIdempotent

Read an unexpired converter preview by previewId. No API key. Returns the title, fields, stages, expiresAt, and previewUrl already shown on the public preview page (/tools/p/{previewId}), whether or not that preview was claimed. Unknown or expired ids are not found and include the converter URL. Does not return organization ids or saved form ids.

Input Schema

NameRequiredDescriptionDefault
previewIdYesPreview id from previewUrl (/tools/p/{previewId}).

Output Schema

NameRequiredDescriptionDefault
titleYes
fieldsYes
stagesYes
expiresAtYesUnix milliseconds when the preview is deleted.
previewUrlYesPublic preview URL, /tools/p/{previewId}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / previewId / description
      Added value: +"Preview id from previewUrl (/tools/p/{previewId})."
    • addedInput schema / properties / previewId / minLength
      Added value: +22
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "expiresAt": {
+      "description": "Unix milliseconds when the preview is deleted.",
+      "type": "integer"
+    },
+    "fields": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "label": {
+            "description": "Field label shown on the preview.",
+            "type": "string"
+          },
+          "type": {
+            "description": "Field type, such as short_text or email.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "previewUrl": {
+      "description": "Public preview URL, /tools/p/{previewId}.",
+      "format": "uri",
+      "type": "string"
+    },
+    "stages": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "kind": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "order": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "name",
+          "kind",
+          "order"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "fields",
+    "stages",
+    "expiresAt",
+    "previewUrl"
+  ],
+  "type": "object"
+}
  3. Changed3 schema fields changed
    • addedInput schema / properties / previewId / maxLength
      Added value: +22
    • removedInput schema / properties / previewId / minLength
      Removed value: -1
    • addedInput schema / properties / previewId / pattern
      Added value: +"^[A-Za-z0-9_-]{21}[AQgw]$"
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real value beyond them: no API key required, the exact returned fields, the /tools/p/{previewId} public page correspondence, the not-found behavior including the converter URL, and an explicit statement that org ids and saved form ids are withheld.

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 sentences, zero filler, with the core operation and the no-API-key note front-loaded. It is slightly dense with return-field enumeration that the output schema already carries, but nothing is wasted or buried.

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 single-parameter read tool with full annotation coverage and an output schema, this description covers authentication, error behavior, scope boundaries, and return shape. Nothing an agent needs to invoke 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% and the single previewId parameter is fully documented in the schema, including the pattern and its source in previewUrl. The description restates the same origin, so it adds no syntax or format detail beyond the schema — baseline 3 is correct.

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+resource (read a converter preview) scoped by previewId, and the 'unexpired' qualifier plus the claim-status note distinguish it from the sibling claim_preview. An agent can tell what this returns 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 Guidelines4/5

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

Makes clear this reads an existing preview whether or not it was claimed, which implicitly routes claiming to claim_preview, and notes unknown/expired ids are not found. It stops short of naming claim_preview as the alternative for the write path or stating prerequisites explicitly.

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

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