FoundRole Jobs - AI Job Search & Application Tracker

Official

by foundrole

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Compare jobs

jobs_compare

Read-only

Compare 2–4 jobs side by side on resume match, missing skills, H-1B and E-Verify signals, ghost-job risk, posted pay, and salary estimates to choose the best fit.

Instructions

Compares 2 to 4 jobs side by side using the same FoundRole analysis fields: resume match, missing skills, H-1B and E-Verify signals, ghost-job risk, posted pay, and market salary estimates.

comparison_refs accepts exact FoundRole job IDs returned by jobs_search and exact external comparisonRef URLs returned by jobs_analyze_external. Analyze each outside job first; a bare URL that has not been analyzed cannot be compared because FoundRole does not have its posting facts. Preserve every reference exactly, keep the user's requested order, and do not send duplicates.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`comparison_refs`	Yes	Two to four exact FoundRole job IDs or external comparisonRef URLs

Output Schema

TableJSON Schema

Name	Required	Description	Default
`jobs`	Yes
`mode`	Yes
`studioUrl`	No
`statusOrder`	Yes
`trackerWebUrl`	Yes
`system_instruction`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.1.16Sep 27, 2026
- removedOutput schema / properties / jobs / items / properties / estimatedSalary / properties / basedOn
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
- addedOutput schema / properties / jobs / items / properties / estimatedSalary / properties / currency
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / studioUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / system_instruction
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedv1.1.9Aug 6, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish this is a read-only, non-destructive, closed-world operation, so the safety profile is covered. The description adds real behavioral context beyond that: a 2-4 reference bound, the requirement to preserve exact reference strings and user order, and a no-duplicates constraint. It stops short of describing what the comparison output looks like, though an output schema exists.

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 core action and field list are front-loaded in the first sentence, with the reference-format guidance second. Two paragraphs with no filler; slightly dense but every sentence carries a constraint the agent must honor.

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 an output schema and full annotation coverage, the description supplies everything else needed: input provenance, prerequisite analysis step, count bounds, ordering, and dedup. 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.

Parameters4/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 with minItems/maxItems, so the baseline is 3. The description adds meaning the schema cannot: the two distinct reference types (FoundRole job IDs vs external comparisonRef URLs), the requirement to pass them exactly, and the ordering/dedup rules.

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 ('compares 2 to 4 jobs side by side') and enumerates the exact analysis dimensions returned (resume match, missing skills, H-1B/E-Verify, ghost-job risk, pay, salary estimates). This clearly separates it from jobs_details and jobs_analyze_external, which handle single jobs.

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?

Explicitly routes the agent: it names jobs_search as the source of job IDs and jobs_analyze_external as the source of external comparisonRef URLs, and states the prerequisite that an outside job must be analyzed first. It also states the failure condition — a bare unanalyzed URL cannot be compared — which is exactly the when-not guidance an agent needs.

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