FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT

by io.github.foundrole

Overview Discussions Admin

List reminders

reminder_list

Read-only

Lists tracked jobs that have reminders set, ordered by reminder time (soonest first).

Input:

limit: Number of results to return (default 20, max 50)

Output: Returns a list of tracked jobs with active reminders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reminder_list"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of results to return (default 20, max 50)

Output Schema

Name	Required	Description	Default
`hasMore`	No
`totalCount`	No
`trackedJobs`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 10, 2026

addedOutput schema / properties / trackedJobs / items / properties / appliedDateUnknown

Added value: +{
+  "description": "True for a job at the applied status with no stored applied date, unless the person said they do not remember it. FoundRole never fills that date in by itself; it comes from the person and tracker_update stores it in applied_at, or records in applied_date_declined that they do not remember it.",
+  "type": "boolean"
+}

addedOutput schema / properties / trackedJobs / items / properties / daysSinceApplied

Added value: +{
+  "description": "Whole days since the applied date, counted in the user's time zone; null without an applied date.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / trackedJobs / items / properties / followUpDay

Added value: +{
+  "description": "Latest follow-up point, in days after applying, that a job still at the applied status has reached; null before the first point and for every other status. FoundRole never moves or archives a job by itself.",
+  "enum": [
+    7,
+    14,
+    21,
+    null
+  ],
+  "type": [
+    "integer",
+    "null"
+  ]
+}

Changed8 schema fields changedJul 21, 2026
- changedOutput schema / properties / trackedJobs / items / properties / appliedAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / createdAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / deadline / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / notes / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / reminderAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / salaryOfferedType / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / subStatus / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / updatedAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed3 schema fields changedJul 20, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedJun 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "hasMore": {
+      "type": "boolean"
+    },
+    "totalCount": {
+      "type": "integer"
+    },
+    "trackedJobs": {
+      "items": {
+        "properties": {
+          "appliedAt": {
+            "type": "string"
+          },
+          "contacts": {
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "createdAt": {
+            "type": "string"
+          },
+          "deadline": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "isStarred": {
+            "type": "boolean"
+          },
+          "notes": {
+            "type": "string"
+          },
+          "reminderAt": {
+            "type": "string"
+          },
+          "salaryOffered": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "salaryOfferedType": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "subStatus": {
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "trackable": {
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "updatedAt": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedJun 3, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior in the ordering rule ('soonest first'), which the schema does not carry. It says nothing about whether the list is paginated beyond the limit cap or what happens when truncated, leaving a modest gap.

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?

The key information is front-loaded in a single sentence, and the bolded Input/Output sections are easy to scan. However, both sections largely duplicate structured fields — the limit text is copied from the schema and the Output block restates what the output schema already provides.

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?

For a one-parameter read-only list tool with a full output schema, the description covers purpose, ordering, and the result cap, which is enough to call it correctly. The only missing piece is truncation behavior when more than 50 reminders exist, a minor gap given the shallow surface.

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 fully documented in the schema, including default 20 and max 50. The description merely restates that text verbatim, adding no new meaning such as how ordering interacts with the limit. Baseline 3 applies.

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 opens with a specific verb and resource: 'Lists tracked jobs that have reminders set', plus the ordering ('soonest first'). That scope distinguishes it from reminder_set and reminder_delete, which mutate reminders. It stops short of naming an alternative explicitly, so it is clear but not sibling-differentiated by reference.

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 only implied: an agent can infer this is the read path for reviewing existing reminders. There is no statement of when to prefer this over sibling listing tools such as tracker_list or job_alert_list, and no prerequisite or exclusion guidance.

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

All FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT 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.