GetMattered

Draft a Follow-up

getmattered_draft_follow_up

Drafts a follow-up for one application. Nothing is sent. Uses AI credits.

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": {
      "application_id": "<application_id>"
    },
    "name": "getmattered_draft_follow_up"
  }
}

Input Schema

Name	Required	Description	Default
`application_id`	Yes	The application, from getmattered_list_due_follow_ups or getmattered_get_applications.

Output Schema

Name	Required	Description
`draft`	Yes	From getmattered_draft_follow_up: the drafted message. Nothing was sent.
`action`	Yes	The operation that ran, one of list, history, draft, send or record_sent.
`history`	Yes	From getmattered_list_sent_follow_ups: follow-ups already sent, newest first.
`recorded`	Yes	From getmattered_send_follow_up or getmattered_record_follow_up: the follow-up count after it was recorded.
`followUps`	Yes	From getmattered_list_due_follow_ups: applications whose follow-up is due, most urgent first.
`setupStep`	No	Present while account setup is open: the first setup step.
`nextCursor`	Yes	From getmattered_list_sent_follow_ups: the cursor value for the next page. Null on the last page.
`confirmToken`	Yes	From getmattered_send_follow_up when nothing was sent yet: the confirm_token value that sends this email, with the same arguments, after the user's yes. Works once, for 10 minutes.
`notConfirmed`	Yes	True when the user declined the confirmation and nothing was sent.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 8, 2026

changedOutput schema / properties / action / description

Previous value: -"The operation that ran: list, history, draft, send or record_sent."New value: +"The operation that ran, one of list, history, draft, send or record_sent."

changedOutput schema / properties / confirmToken / description

Previous value: -"From getmattered_send_follow_up when nothing was sent yet: show the user the email, then pass this as confirm_token with the same arguments after their yes. Works once, for 10 minutes."New value: +"From getmattered_send_follow_up when nothing was sent yet: the confirm_token value that sends this email, with the same arguments, after the user's yes. Works once, for 10 minutes."

changedOutput schema / properties / followUps / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "applicationId": {
-          "description": "Pass as application_id to getmattered_draft_follow_up, getmattered_send_follow_up or getmattered_record_follow_up.",
-          "type": "number"
-        },
-        "company": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "followUpCount": {
-          "type": "number"
-        },
-        "jobTitle": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "lastFollowUpAt": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "nextFollowUpDueAt": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "urgency": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "applicationId",
-        "jobTitle",
-        "company",
-        "urgency",
-        "followUpCount",
-        "lastFollowUpAt",
-        "nextFollowUpDueAt"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "applicationId": {
+          "description": "The application_id getmattered_draft_follow_up, getmattered_send_follow_up and getmattered_record_follow_up take.",
+          "type": "number"
+        },
+        "company": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "followUpCount": {
+          "type": "number"
+        },
+        "jobTitle": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "lastFollowUpAt": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "nextFollowUpDueAt": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "urgency": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "applicationId",
+        "jobTitle",
+        "company",
+        "urgency",
+        "followUpCount",
+        "lastFollowUpAt",
+        "nextFollowUpDueAt"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / nextCursor / description

Previous value: -"From getmattered_list_sent_follow_ups: pass as cursor for the next page. Null on the last page."New value: +"From getmattered_list_sent_follow_ups: the cursor value for the next page. Null on the last page."

changedOutput schema / properties / setupStep / description

Previous value: -"Set while account setup is open: the step to take first."New value: +"Present while account setup is open: the first setup step."

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / setupStep

Added value: +{
+  "description": "Set while account setup is open: the step to take first.",
+  "type": "string"
+}

Changed2 schema fields changedOct 31, 2026

addedOutput schema / properties / confirmToken

Added value: +{
+  "description": "From getmattered_send_follow_up when nothing was sent yet: show the user the email, then pass this as confirm_token with the same arguments after their yes. Works once, for 10 minutes.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "action",
-  "followUps",
-  "history",
-  "nextCursor",
-  "draft",
-  "recorded",
-  "notConfirmed"
-]New value: +[
+  "action",
+  "followUps",
+  "history",
+  "nextCursor",
+  "draft",
+  "recorded",
+  "notConfirmed",
+  "confirmToken"
+]

AddedOct 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the annotations, the description discloses two behaviors an agent could not infer: the operation produces a draft without transmitting anything ('Nothing is sent'), and it consumes AI credits, which is a real cost consideration. It does not say whether drafts persist or how long they last, keeping it below a 5.

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 very short sentences, front-loaded with the core action, followed by the two facts that matter most (no send, credit cost). Zero 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?

An output schema exists, so return values need no explanation, and the single parameter is fully documented in the schema. The description covers cost and the non-sending nature, leaving only a minor gap about what to do with the draft afterward.

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 parameter is documented there, including where to obtain the id from getmattered_list_due_follow_ups or getmattered_get_applications. The description only reinforces the single-application scope, adding no syntax or format detail beyond the schema.

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 ('Drafts a follow-up') and scopes it to 'one application', which separates it from the batch listing siblings like list_due_follow_ups. 'Nothing is sent' further distinguishes it from send_follow_up, though that sibling is not named.

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?

The phrase 'Nothing is sent' implies this is the preview step before send_follow_up, but the description never states when to choose this over send_follow_up or record_follow_up. Usage is implied rather than explicit, with no named alternatives or preconditions.

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

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