Openings

Analyze fit for one job

analyze_job_fit

Read-onlyIdempotent

Explain how one job fits a resume: which requirements the resume supports, which it does not, the screening risks, and what to prepare for an interview, each tied to text quoted from the resume rather than inferred. Use it after search_jobs or recommend_jobs has produced a job id and the candidate wants depth on a single role instead of a list. The resume is parsed in memory for this call and never stored.

Input Schema

TableJSON Schema

Name	Required	Description
`jobId`	Yes	Stable job id from search_jobs or recommend_jobs
`intent`	No	What the candidate is actually looking for, stated explicitly rather than guessed from the resume. Every field is optional; the ones given narrow the result, and the excluded* fields remove roles the candidate does not want to see.
`resume`	Yes	The resume itself, passed inline. It is parsed in memory for this call and never written to disk, logged, or sent anywhere else.

Output Schema

TableJSON Schema

Name	Required	Description
`job`	Yes	The job that was analyzed
`scores`	No
`profile`	No	What was read from the resume; not stored
`supported`	No	Requirements the resume supports, each with the quoted evidence
`assessment`	Yes	The overall read, with its reasoning
`unsupported`	No	Requirements the resume does not evidence at all
`screeningRisks`	No	What is likely to stop this application early
`partiallySupported`	No	Requirements with partial evidence, and what is missing
`interviewPreparationGaps`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedSep 22, 2026

addedInput schema / properties / intent / description

Added value: +"What the candidate is actually looking for, stated explicitly rather than guessed from the resume. Every field is optional; the ones given narrow the result, and the excluded* fields remove roles the candidate does not want to see."

addedInput schema / properties / intent / properties / countries / description

Added value: +"Two-letter codes the candidate may work in, such as IN or US. This is eligibility to work, not where the office is"

addedInput schema / properties / intent / properties / excludedCountries / description
```
Added value: +"Two-letter codes to drop even when a role is otherwise eligible"
```
addedInput schema / properties / intent / properties / excludedLocations / description
```
Added value: +"Cities or regions to drop, matched like locations"
```
addedInput schema / properties / intent / properties / excludedRoles / description
```
Added value: +"Role titles to drop, matched like roles"
```

addedInput schema / properties / intent / properties / excludedTerms / description

Added value: +"Words that disqualify a role, matched as whole words in the title, such as \"intern\" or \"sales\""

addedInput schema / properties / intent / properties / locations / description

Added value: +"Cities or regions to keep, matched as case-insensitive substrings of the job's location, such as \"Bengaluru\" or \"Delhi NCR\""

addedInput schema / properties / intent / properties / remote / description

Added value: +"True to keep only remote roles, false to drop them; omit to keep both"

addedInput schema / properties / intent / properties / requiredSkills / description

Added value: +"Skills a role must state to be kept, such as \"kubernetes\". Each is matched as a whole word"

addedInput schema / properties / intent / properties / roles / description

Added value: +"Role titles the candidate is looking for, in their own words, such as \"backend engineer\" or \"data analyst\". Matched against the job title"

addedInput schema / properties / intent / properties / seniority / description

Added value: +"Levels to keep, in the posting's own vocabulary, such as \"senior\" or \"lead\". Not a years-of-experience filter: use experienceYears in search_jobs for that"

addedInput schema / properties / jobId / description

Added value: +"Stable job id from search_jobs or recommend_jobs"

addedInput schema / properties / resume / description

Added value: +"The resume itself, passed inline. It is parsed in memory for this call and never written to disk, logged, or sent anywhere else."

addedInput schema / properties / resume / properties / format / description

Added value: +"How content is encoded: plain text, markdown, or base64 of a PDF or DOCX file"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "assessment": {
+      "additionalProperties": true,
+      "description": "The overall read, with its reasoning",
+      "type": "object"
+    },
+    "interviewPreparationGaps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "job": {
+      "additionalProperties": true,
+      "description": "The job that was analyzed",
+      "properties": {
+        "age": {
+          "description": "Bucketed posting age; undated means the board gave no date, not that the role is fresh",
+          "enum": [
+            "new",
+            "older",
+            "stale",
+            "undated"
+          ],
+          "type": "string"
+        },
+        "company": {
+          "type": "string"
+        },
+        "eligibleCountries": {
+          "description": "Two-letter codes the role is open to",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "experience": {
+          "additionalProperties": true,
+          "description": "Years the posting itself states as { min, max }; null when it states none, absent when the description was not read",
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "Stable id to pass to get_job, analyze_job_fit or optimize_resume",
+          "type": "string"
+        },
+        "location": {
+          "type": "string"
+        },
+        "postedDaysAgo": {
+          "type": "number"
+        },
+        "remote": {
+          "type": "boolean"
+        },
+        "title": {
+          "type": "string"
+        },
+        "updatedAt": {
+          "description": "When the board says the role was posted or last updated; absent when the board states none",
+          "type": "string"
+        },
+        "url": {
+          "description": "The employer's own posting, which is where an application is made",
+          "type": "string"
+        },
+        "workMode": {
+          "enum": [
+            "remote",
+            "hybrid",
+            "onsite",
+            "unknown"
+          ],
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "partiallySupported": {
+      "description": "Requirements with partial evidence, and what is missing",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "profile": {
+      "additionalProperties": true,
+      "description": "What was read from the resume; not stored",
+      "type": "object"
+    },
+    "scores": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "screeningRisks": {
+      "description": "What is likely to stop this application early",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "supported": {
+      "description": "Requirements the resume supports, each with the quoted evidence",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "unsupported": {
+      "description": "Requirements the resume does not evidence at all",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "job",
+    "assessment"
+  ],
+  "type": "object"
+}

First observedSep 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds high-value behavioral context: it emphasizes that analysis must be grounded in quoted resume text ('rather than inferred'), and it explicitly states the resume is parsed in memory and never stored, which is critical for privacy-sensitive operations. This goes beyond annotations and builds trust, though it could also mention error behavior or return format.

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 tightly written and front-loaded: the first sentence captures the core purpose and constraints, then immediately gives usage context, and ends with a critical privacy note. Every sentence contributes value without redundancy, making efficient use of the reader's attention.

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?

The description is complete for its complexity: it explains what output to expect (requirements supported/not, risks, interview prep), ties to sibling workflow, and addresses privacy. The output schema exists, so return format details are omitted appropriately. Minor gaps include not mentioning potential errors or handling of invalid job ids, but the provided info suffices for correct invocation.

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%, with rich descriptions for all parameters, including jobId and resume. The description adds little parameter-specific detail beyond what the schema provides, but it reiterates that the resume is passed inline and references the job id provenance. It does not introduce new syntax or clarify edge cases not already in schema, so the baseline 3 is appropriate.

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?

The description clearly states the specific verb ('analyze') and resource ('one job') with a precise scope: it evaluates requirements, screening risks, and interview prep, and specifies that claims must be quoted from the resume, not inferred. It distinguishes itself from list-returning siblings like search_jobs and recommend_jobs by describing the depth and use case, so an agent can immediately differentiate it.

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?

The description explicitly states when to use it: 'after search_jobs or recommend_jobs has produced a job id and the candidate wants depth on a single role instead of a list.' It implies not to use it for listing jobs and mentions the sibling tool relationship. This direct, actionable guidance leaves no ambiguity about the tool's role in the workflow.

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

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