Skip to main content
Glama
TVLSS

HireJack

Skill Gap

skill_gap
Read-only

Analyze the gap between your current skills and the requirements of your desired role. See your match percentage, skills you already have, and missing skills ranked by impact to prioritize what to learn next.

Instructions

Analyze the gap between the authenticated user's current skills and what their desired roles require in the live market. Pro tier. Returns matchPct (0-100), the list of skills the user already has that map to their target roles, and the list of missing skills ranked by impact (how often the skill appears in target-role postings). Use for 'what should I learn next?' or 'how close am I to senior PM roles?'. Not for simulating the payoff of skills the user might LEARN — use skill_impact for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesGap between the user's skills and their desired roles' requirements
metaNoRequest/response metadata (pagination cursors, snapshot timestamps, applied filters)
citation_urlNohirejack.com URL to cite when surfacing this result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.5
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "citation_url": {
      +      "description": "hirejack.com URL to cite when surfacing this result",
      +      "type": "string"
      +    },
      +    "data": {
      +      "additionalProperties": true,
      +      "description": "Gap between the user's skills and their desired roles' requirements",
      +      "properties": {
      +        "learnDisclosure": {
      +          "description": "Affiliate-link disclosure text when learn links are present",
      +          "nullable": true,
      +          "type": "string"
      +        },
      +        "matchPct": {
      +          "description": "Share of target-role skills the user already has, 0-100",
      +          "type": "number"
      +        },
      +        "matchedSkills": {
      +          "description": "User skills that map to their desired roles",
      +          "items": {
      +            "additionalProperties": true,
      +            "properties": {
      +              "id": {
      +                "type": "string"
      +              },
      +              "name": {
      +                "type": "string"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "message": {
      +          "description": "Present (with matchPct 0) when the profile lacks skills or desired roles",
      +          "type": "string"
      +        },
      +        "missingSkills": {
      +          "description": "Skills the desired roles require that the user lacks, most impactful first",
      +          "items": {
      +            "additionalProperties": true,
      +            "properties": {
      +              "id": {
      +                "description": "Skill id from codex/skills.json",
      +                "type": "string"
      +              },
      +              "learn": {
      +                "additionalProperties": true,
      +                "description": "Learning resources for the skill, when known",
      +                "nullable": true,
      +                "properties": {
      +                  "alternates": {
      +                    "items": {
      +                      "additionalProperties": true,
      +                      "properties": {},
      +                      "type": "object"
      +                    },
      +                    "type": "array"
      +                  },
      +                  "primary": {
      +                    "additionalProperties": true,
      +                    "description": "Recommended course link (provider, url, title, free, ...)",
      +                    "nullable": true,
      +                    "properties": {},
      +                    "type": "object"
      +                  }
      +                },
      +                "type": "object"
      +              },
      +              "name": {
      +                "type": "string"
      +              },
      +              "roles": {
      +                "description": "The desired-role titles that require it",
      +                "items": {
      +                  "type": "string"
      +                },
      +                "type": "array"
      +              },
      +              "rolesNeeding": {
      +                "description": "How many of the user's desired roles require it (impact rank)",
      +                "type": "number"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "topGaps": {
      +          "description": "Top 5 of missingSkills",
      +          "items": {
      +            "additionalProperties": true,
      +            "properties": {
      +              "id": {
      +                "description": "Skill id from codex/skills.json",
      +                "type": "string"
      +              },
      +              "learn": {
      +                "additionalProperties": true,
      +                "description": "Learning resources for the skill, when known",
      +                "nullable": true,
      +                "properties": {
      +                  "alternates": {
      +                    "items": {
      +                      "additionalProperties": true,
      +                      "properties": {},
      +                      "type": "object"
      +                    },
      +                    "type": "array"
      +                  },
      +                  "primary": {
      +                    "additionalProperties": true,
      +                    "description": "Recommended course link (provider, url, title, free, ...)",
      +                    "nullable": true,
      +                    "properties": {},
      +                    "type": "object"
      +                  }
      +                },
      +                "type": "object"
      +              },
      +              "name": {
      +                "type": "string"
      +              },
      +              "roles": {
      +                "description": "The desired-role titles that require it",
      +                "items": {
      +                  "type": "string"
      +                },
      +                "type": "array"
      +              },
      +              "rolesNeeding": {
      +                "description": "How many of the user's desired roles require it (impact rank)",
      +                "type": "number"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "meta": {
      +      "additionalProperties": true,
      +      "description": "Request/response metadata (pagination cursors, snapshot timestamps, applied filters)",
      +      "properties": {},
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "data"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.6

TDQS

A4.9/5.0
Behavior5/5

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

Description adds significant behavioral context beyond annotations: explains return values (matchPct, map of skills, missing skills ranked by impact). Annotations already indicate readOnlyHint, and description does not contradict it.

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?

Three sentences with no fluff: first sentence states purpose, second details outputs, third gives usage guidelines. Front-loaded and efficient.

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?

Despite zero parameters and output schema present, the description fully explains what the tool returns and when to use it. Sibling tools provide context. No gaps.

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?

No parameters defined, so schema coverage is 100% vacuously. Baseline for 0 params is 4; description has no need to add param info.

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 tool analyzes the gap between the authenticated user's current skills and desired role requirements in the live market. It uses a specific verb ('Analyze') and resource ('gap'), and distinguishes from sibling tool 'skill_impact'.

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 provides use cases ('what should I learn next?', 'how close am I to senior PM roles?') and tells when NOT to use it ('Not for simulating...'), directing to alternative 'skill_impact'. Also mentions 'Pro tier' as context.

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