Apply2Volunteer

Convert a PDF for the organization

convert_pdf_preview

Convert a PDF URL into a stored preview for the authenticated organization. Requires an org API key with the forms:read scope. Returns the preview id and expiry. For a preview without a key, use preview_volunteer_form.

Input Schema

Name	Required	Description	Default
`url`	Yes	https URL of a blank volunteer PDF.

Output Schema

Name	Required	Description
`title`	Yes
`fields`	Yes	Number of parsed fields.
`grader`	Yes
`expiresAt`	Yes
`previewId`	Yes	Preview id. The public path is /tools/p/{previewId}.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / properties / url / description
```
Added value: +"https URL of a blank volunteer PDF."
```

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "expiresAt": {
+      "type": "integer"
+    },
+    "fields": {
+      "description": "Number of parsed fields.",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "grader": {
+      "additionalProperties": true,
+      "properties": {
+        "grade": {
+          "enum": [
+            "A",
+            "B",
+            "C",
+            "D",
+            "F"
+          ],
+          "type": "string"
+        },
+        "recommendations": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "detail": {
+                "type": "string"
+              },
+              "id": {
+                "type": "string"
+              },
+              "severity": {
+                "type": "string"
+              },
+              "title": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "severity",
+              "title",
+              "detail"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "score": {
+          "maximum": 100,
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "score",
+        "grade",
+        "recommendations"
+      ],
+      "type": "object"
+    },
+    "previewId": {
+      "description": "Preview id. The public path is /tools/p/{previewId}.",
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "fields",
+    "grader",
+    "previewId",
+    "expiresAt"
+  ],
+  "type": "object"
+}

First observedOct 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the description's real added value is the auth requirement (org API key with forms:read scope) and the fact that this persists a stored preview with an expiry. It could say more about what happens on re-conversion or expiry, but the key behavioral context is present.

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?

Three short sentences leading with the action, then the prerequisite, then the alternative routing. No filler and every sentence carries information an agent needs.

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?

An output schema exists, so return-value detail is not the description's burden, yet it still flags the preview id and expiry. With annotations covering safety and the schema covering the parameter, nothing needed for a correct call 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 coverage is 100% for the single url parameter, which the schema already documents as an https URL of a blank volunteer PDF. The description restates 'PDF URL' without adding format, size, or validation constraints beyond what the schema provides, so the baseline of 3 applies.

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 (convert a PDF URL into a stored preview) scoped to the authenticated organization, which distinguishes it from generic PDF-adjacent siblings like create_form_from_pdf. It explicitly names preview_volunteer_form as the related-but-different tool, so the agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives the prerequisite (org API key with forms:read scope) and an explicit alternative with its selecting condition: use preview_volunteer_form when no key is available. That is a clear when/when-not/alternative statement rather than an implied usage note.

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?