signaltender-mcp

Audit Key Personnel LCAT Qualifications & Tailor Shipley Resume + LOC

match_key_personnel

Read-onlyIdempotent

Evaluate a candidate's resume against RFP Section L/M Key Personnel and GSA MAS / OASIS+ / Alliant 3 Labor Category (LCAT) requirements (years of experience, education, security clearance, DoD 8570/8140 certifications), rewrite relevant roles into a Shipley Key Personnel bio, and generate a ready-to-sign Letter of Commitment (LOC). This is a read-only, stateless qualification audit and resume formatter that does not store candidate PII (requires X-RapidAPI-Key; allow_education_experience_substitution [default true] applies standard federal GSA/OPM equivalency rules such as Bachelor's + 4 years = Master's when scoring eligibility). Use this tool when qualifying and formatting individual Key Personnel resumes for a proposal; use match_capability_statement instead to score overall company-level Bid/No-Bid Pwin, or generate_cpars_past_performance for company-level contract citations.

Input Schema

Name	Required	Description
`candidate_resume_text`	Yes	Candidate's unstructured resume or CV including education degrees, active security clearances, professional certifications (CISSP, PMP, AWS, etc.), and chronological work history.
`lcat_or_rfp_requirements`	Yes	Raw RFP Section L/M Key Personnel instructions, GSA MAS / GWAC Labor Category (LCAT) minimum qualifications, required security clearance, and mandatory DoD 8570/8140 certifications.
`allow_education_experience_substitution`	No	When true (default), applies standard federal GSA/OPM degree-for-experience substitution rules (e.g., Bachelor's + 4 additional years of specialized experience satisfies a Master's requirement) unless the RFP text explicitly prohibits substitutions.

Output Schema

Name	Required	Description
`target_lcat_title`	No	Normalized Labor Category (LCAT) and Key Personnel role title extracted from the solicitation.
`lcat_compliance_audit`	No	Granular verification of years of experience, degree equivalency, security clearance, and DoD 8570/8140 certifications.
`qualification_verdict`	No	Audit verdict: 'FULLY_QUALIFIED_COMPLIANT', 'QUALIFIED_VIA_SUBSTITUTION', 'WAIVER_OR_CERT_PENDING', or 'DISQUALIFIED_HARD_KNOCKOUT'.
`overall_qualification_score`	No	Quantitative Key Personnel & LCAT qualification score (0-100).
`tailored_shipley_resume_profile`	No	Proposal-ready Shipley Key Personnel bio, rewritten past-performance bullets, and ready-to-sign Letter of Commitment (LOC).
`requirement_by_requirement_matrix`	No	Line-by-line compliance checklist mapping each RFP Key Personnel mandate to candidate resume evidence.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 29, 2026

removedOutput schema / properties / compliance_verdict

Removed value: -{
-  "description": "Eligibility status (FULLY_QUALIFIED, QUALIFIED_VIA_SUBSTITUTION, NON_COMPLIANT_GAP).",
-  "type": "string"
-}

addedOutput schema / properties / lcat_compliance_audit

Added value: +{
+  "description": "Granular verification of years of experience, degree equivalency, security clearance, and DoD 8570/8140 certifications.",
+  "type": "object"
+}

removedOutput schema / properties / letter_of_commitment_loc

Removed value: -{
-  "description": "Ready-to-sign Key Personnel Letter of Commitment (LOC) template.",
-  "type": "string"
-}

addedOutput schema / properties / overall_qualification_score

Added value: +{
+  "description": "Quantitative Key Personnel & LCAT qualification score (0-100).",
+  "type": "integer"
+}

removedOutput schema / properties / qualification_score

Removed value: -{
-  "description": "Candidate LCAT/Key Personnel compliance score from 0 to 100.",
-  "type": "integer"
-}

addedOutput schema / properties / qualification_verdict

Added value: +{
+  "description": "Audit verdict: 'FULLY_QUALIFIED_COMPLIANT', 'QUALIFIED_VIA_SUBSTITUTION', 'WAIVER_OR_CERT_PENDING', or 'DISQUALIFIED_HARD_KNOCKOUT'.",
+  "type": "string"
+}

removedOutput schema / properties / requirement_audit_matrix

Removed value: -{
-  "description": "Line-by-line audit of education, years of experience, clearance, and certification mandates.",
-  "items": {
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / requirement_by_requirement_matrix

Added value: +{
+  "description": "Line-by-line compliance checklist mapping each RFP Key Personnel mandate to candidate resume evidence.",
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / tailored_shipley_resume_markdown

Removed value: -{
-  "description": "Rewritten Shipley Key Personnel biographical sketch and compliance-mapped experience bullets.",
-  "type": "string"
-}

addedOutput schema / properties / tailored_shipley_resume_profile

Added value: +{
+  "description": "Proposal-ready Shipley Key Personnel bio, rewritten past-performance bullets, and ready-to-sign Letter of Commitment (LOC).",
+  "type": "object"
+}

addedOutput schema / properties / target_lcat_title

Added value: +{
+  "description": "Normalized Labor Category (LCAT) and Key Personnel role title extracted from the solicitation.",
+  "type": "string"
+}

Changed8 schema fields changedOct 21, 2026

addedInput schema / properties / allow_education_experience_substitution / description

Added value: +"When true (default), applies standard federal GSA/OPM degree-for-experience substitution rules (e.g., Bachelor's + 4 additional years of specialized experience satisfies a Master's requirement) unless the RFP text explicitly prohibits substitutions."

changedInput schema / properties / candidate_resume_text / description

Previous value: -"Candidate's raw resume, CV, security clearance level, certifications, education, and work history."New value: +"Candidate's unstructured resume or CV including education degrees, active security clearances, professional certifications (CISSP, PMP, AWS, etc.), and chronological work history."

addedInput schema / properties / candidate_resume_text / maxLength
```
Added value: +100000
```
addedInput schema / properties / candidate_resume_text / minLength
```
Added value: +40
```

changedInput schema / properties / lcat_or_rfp_requirements / description

Previous value: -"Raw RFP Section L/M Key Personnel requirements, GSA LCAT minimums, clearance mandates, and DoD 8570/8140 certification criteria."New value: +"Raw RFP Section L/M Key Personnel instructions, GSA MAS / GWAC Labor Category (LCAT) minimum qualifications, required security clearance, and mandatory DoD 8570/8140 certifications."

addedInput schema / properties / lcat_or_rfp_requirements / maxLength
```
Added value: +80000
```
addedInput schema / properties / lcat_or_rfp_requirements / minLength
```
Added value: +30
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "compliance_verdict": {
+      "description": "Eligibility status (FULLY_QUALIFIED, QUALIFIED_VIA_SUBSTITUTION, NON_COMPLIANT_GAP).",
+      "type": "string"
+    },
+    "letter_of_commitment_loc": {
+      "description": "Ready-to-sign Key Personnel Letter of Commitment (LOC) template.",
+      "type": "string"
+    },
+    "qualification_score": {
+      "description": "Candidate LCAT/Key Personnel compliance score from 0 to 100.",
+      "type": "integer"
+    },
+    "requirement_audit_matrix": {
+      "description": "Line-by-line audit of education, years of experience, clearance, and certification mandates.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tailored_shipley_resume_markdown": {
+      "description": "Rewritten Shipley Key Personnel biographical sketch and compliance-mapped experience bullets.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld=false, and the description goes further by disclosing statelessness, non-retention of candidate PII, and an auth requirement (X-RapidAPI-Key) that appears nowhere in the schema. What it omits is the shape of the returned audit verdict (scored, and against what threshold), so it stops short of a 5.

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?

Three sentences, front-loaded with the action and its inputs before the output list, then safety/auth caveats, then routing. Dense but every clause is doing work; the parenthetical equivalency example and the auth key note are the only parts that could be trimmed.

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?

Given three parameters, full schema coverage, a present output schema, and rich annotations, the description supplies everything an agent still needs: the three artifacts produced, the stateless/no-PII guarantee, the API-key prerequisite, and sibling routing. No material gap remains 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 description coverage is 100%, so all three parameters are already documented, and the description largely restates them. The 'Bachelor's + 4 years = Master's when scoring eligibility' gloss mirrors the schema's own wording for allow_education_experience_substitution rather than adding new meaning. Baseline 3 applies when the schema carries the load.

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?

Specific verb+resource: 'Evaluate a candidate's resume against RFP Section L/M Key Personnel and GSA MAS / OASIS+ / Alliant 3 LCAT requirements', plus three named outputs (audit, Shipley bio, LOC). It explicitly distinguishes itself from match_capability_statement (company-level Pwin) and generate_cpars_past_performance (contract citations), so an agent can route without opening any schema.

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?

Contains an explicit 'Use this tool when qualifying and formatting individual Key Personnel resumes for a proposal' plus two named alternatives with the condition that selects each ('use X instead to score overall company-level Bid/No-Bid Pwin'). When-to-use, when-not, and alternatives are all present.

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

All signaltender-mcp 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.

Resources

Need Help?