Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Analyze skill gaps

skill_gap_analysis
Read-onlyIdempotent

Compare a public Jobiba job skills list with the candidate profile.

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": {
      "jobId": "<jobId>"
    },
    "name": "skill_gap_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one useful behavioral fact — that the comparison draws on a public Jobiba job skills list versus the stored candidate profile — but says nothing about what happens if no profile exists or what the comparison yields. With annotations carrying the behavior burden, this is minimally adequate.

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?

A single short sentence with no filler, so nothing needs trimming. Its brevity is not paired with front-loading of any actionable detail, but as a structure it is clean.

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

Completeness2/5

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

For a simple one-parameter read tool this is thin: the only parameter is undocumented, the required candidate-profile precondition is unstated, and no output schema exists to explain what a "comparison" returns. An agent could call it, but not confidently predict the result.

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% for the single parameter, so the description must compensate and does not — jobId is never mentioned and its format is left unstated. It is unclear whether it is a Jobiba internal ID or an external listing ID, which matters for correct invocation.

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?

The description names a specific verb ("Compare") and two concrete resources (the job's public skills list and the candidate profile), so the operation is identifiable. However, it does not state the outcome — the title says "Analyze skill gaps" but the description never mentions gaps, and nothing distinguishes it from overlapping siblings such as job_match_score or suggest_skills.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of a prerequisite (an existing candidate profile), and no reference to alternative tools that also evaluate fit against a job. The agent must infer the routing decision from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.