Lovie Company Formation

Run Election83b Reminders

formation_run_election83b_reminders

RunElection83bReminders runs the 83(b) reminder sweep (not-started nudges + deadline-relative sign/file reminders + late notice). Reviewer-only; also run in-process by the scheduled cron subcommand.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`dryRun`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`sent`	No
`errors`	No
`scanned`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 10, 2026

addedOutput schema / properties / errors / items / properties / formationId / anyOf

Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / errors / items / properties / formationId / description
```
Removed value: -"UUID value wrapper."
```
removedOutput schema / properties / errors / items / properties / formationId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
removedOutput schema / properties / errors / items / properties / formationId / type
```
Removed value: -"object"
```

addedOutput schema / properties / sent / items / properties / formationId / anyOf

Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / sent / items / properties / formationId / description
```
Removed value: -"UUID value wrapper."
```
removedOutput schema / properties / sent / items / properties / formationId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
removedOutput schema / properties / sent / items / properties / formationId / type
```
Removed value: -"object"
```

First observedAug 11, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations include destructiveHint=false and openWorldHint=false, but no readOnlyHint. The description adds that it's reviewer-only and used by a scheduled cron subcommand, which is useful. However, it doesn't disclose the side effects of running the sweep (e.g., sending emails, marking statuses) or explain the dryRun parameter's behavior, so it doesn't fully compensate for the limited annotation coverage.

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?

The description is a single sentence, tightly packed with all the key information about the sweep's components and access restrictions. It has no fluff or redundant phrasing; every word contributes to understanding the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (1 boolean param, no required fields, output schema exists), so the description is nearly sufficient. However, the absence of any explanation for dryRun (whether it prevents actual sending, what 'dry run' means in this context) makes it incomplete for safe invocation. The description covers the 'what' but not the 'how to control it'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has a single boolean parameter, dryRun, with 0% schema description coverage. The description does not mention dryRun at all, leaving its purpose completely unspecified. Since the description carries the burden for parameter explanation, this is a critical gap.

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?

The description clearly states the tool performs an 83(b) reminder sweep and enumerates the specific reminder types (not-started nudges + deadline-relative sign/file reminders + late notice), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like signature_run_reminders, though the 83(b) context makes it distinct.

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

Usage Guidelines2/5

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

The description mentions 'Reviewer-only' and that it is also run by a cron subcommand, which gives some operational context, but it provides no guidance on when to use this tool vs alternative reminder or formation tools. There are no explicit exclusions or conditions for selection, leaving the agent to infer.

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

All Lovie Company Formation 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.