FoundRole Jobs - AI Job Search & Application Tracker

Official

by foundrole

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Check how hiring software reads a resume

resume_check

Read-onlyIdempotent

Check if your resume text is machine-readable by identifying sections, skills, and dates. Get a readability band and parsed findings to fix gaps.

Instructions

Checks resume text for machine-readable sections, recognized skills, contact channels, a headline, and experience date ranges using FoundRole's deterministic parser.

Pass resume_text to check plain text supplied in the conversation. If resume_text is omitted, the tool reads the previously extracted text of the primary resume in the authenticated user's FoundRole account. It returns a readability band (strong, good, partial), parsed facts, and findings. This is FoundRole's text-readability assessment, not a test against a named ATS, a hiring prediction, or a file-layout check. Pasted text does not preserve the original PDF or DOCX layout.

The tool does not upload a file, create a saved resume or report, change the user's profile, submit an application, or fetch URLs found in the text. It may return a FoundRole website link; opening that link and uploading or editing a resume are separate user actions. Operational request records and diagnostics may retain tool inputs; this tool does not promise that submitted text is never stored.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`resume_text`	No	Plain text of the resume to check, when it is available in the conversation. Omit to check the resume uploaded to the user's FoundRole account. Minimum 200 characters.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`band`	No
`mode`	Yes
`findings`	No
`parsedAs`	No
`uploadUrl`	No
`studioReportUrl`	No
`system_instruction`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.16Sep 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes well beyond them: no file upload, no saved resume or report, no profile change, no application submission, no URL fetching, plus a candid retention caveat and a note that returned website links require separate user action. That is unusually rich behavioral disclosure for a read tool.

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?

Four short paragraphs, front-loaded with purpose, then input behavior, then scope exclusions, then side-effect disclaimers. Every sentence carries information, though the negative-capability list is somewhat exhaustive and could be tightened slightly.

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?

With an output schema present, return values need not be explained, yet the description still summarizes the readability band and outputs. Combined with the input fallback semantics and full side-effect disclosure, nothing an agent needs to call this correctly is missing.

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 optional parameter is fully documented there, including the minimum-length constraint. The description restates the pass/omit behavior but adds no syntax, format, or constraint detail beyond the schema, so the baseline of 3 applies.

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 ('checks resume text for machine-readable sections, recognized skills, contact channels, a headline, and experience date ranges') and names the mechanism (FoundRole's deterministic parser). It also explicitly carves out what it is not (ATS test, hiring prediction, file-layout check), so an agent can distinguish it from analysis-adjacent siblings like jobs_analyze_external.

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?

Gives an explicit branch: pass resume_text when the text is in the conversation, omit it to use the stored primary resume. It further names exclusions ('not a test against a named ATS, a hiring prediction, or a file-layout check') and notes the layout caveat for pasted text, which routes the agent correctly for edge cases.

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