Skip to main content
Glama

Analyze Job Posting Skills

analyze_job_posting_skills
Read-onlyIdempotent

Normalize a job title and extract skills explicitly stated in the title or description, without inferring occupation skills. Use confidence thresholds and versioned title/skill data for analysis.

Instructions

Normalize a title and extract skills explicitly present in its title/description. Does not infer occupation skills. version controls Titles; skills_version controls Skills.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_title": "<job_title>",
      "job_description": "<job_description>"
    },
    "name": "analyze_job_posting_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNolatest
job_titleYes
skills_versionNolatest
job_descriptionYes
confidence_thresholdNo
extract_from_descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds useful behavioral scope (extraction is literal, not inferential) and the version/skills_version coupling, but says nothing about how confidence_threshold affects the returned skills or that the two version parameters move independently of the posting data.

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 short sentences, front-loaded with the core action before the scope exclusion and the parameter mapping. No filler, though the phrase 'a title' is slightly loose given there is an explicit job_title parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, for a 6-parameter tool with zero schema documentation, the description leaves the two most behavior-shaping knobs (confidence_threshold, extract_from_description) unexplained, which is a real gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 6 parameters, so the description carries the full burden. It only disambiguates version (Titles) versus skills_version (Skills); confidence_threshold, extract_from_description and the title/description split are entirely undocumented, and the meaning of 'latest' is never clarified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verbs and resources: normalize a title and extract skills explicitly present in title/description. The exclusion 'Does not infer occupation skills' sharpens the boundary against inference-style siblings, but the definition never distinguishes itself from the near-identically named normalize_title_and_extract_skills and normalize_title_and_get_skills, so the agent cannot tell which combined tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The negative scope ('does not infer occupation skills') is genuine usage guidance that steers an agent away from this tool when inference is wanted, but there is no positive when-to-use statement and no named alternative for title-only normalization (normalize_job_title) or text-only extraction (extract_skills_from_text).

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