Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Skills I should add

suggest_skills
Read-onlyIdempotent

Lists skills most requested by live jobs for a target role that are not on the profile, with demand percentage and how much more pay ads that ask for each list (compared within the same experience level). Suggestions reflect job listings, not the candidate's abilities, and never what learning a skill would pay.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "suggest_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetRoleNoRole to target (defaults to the profile's first target role).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this a safe, read-only, closed-world, idempotent read, so the description does not need to restate that. It adds real value instead: it discloses that recommendations come from live listings rather than the candidate's abilities, that the pay comparison is constrained to the same experience level, and that this is not an estimate of what learning the skill would pay. Those caveats prevent two plausible misinterpretations. It says nothing about result count, ordering, or what happens if the profile lacks a target role.

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?

One dense sentence, front-loaded with the core action ('Lists skills most requested by live jobs...') and the exclusion follows immediately. The trailing caveats are useful but make the sentence long; a second short sentence separating the interpretation limits would read more cleanly.

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?

There is no output schema, and the description does well to describe what is returned (skills, demand percentage, pay premium), which is the main gap it must cover. However, for a read-only recommendation tool with no output schema, it omits ordering, result limits, and the behavior when no target role exists, leaving the agent unclear on what it will actually get back.

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?

With a single parameter at 100% schema description coverage, the schema already documents targetRole and its default. The description restates 'for a target role' but adds no format, syntax, or fallback details 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.

Purpose4/5

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

Names a specific verb and resource ('Lists skills most requested by live jobs') and narrows scope to skills 'not on the profile', which separates it from profile-wide gap tools. It also states the two returned metrics (demand percentage, pay premium), so the agent knows the shape of the answer. It never names a sibling such as skill_gap_analysis, so differentiation is implied rather than explicit.

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?

Usage is only implied: an agent can infer this is the tool for 'which skills should I add', but there is no statement of when to prefer it over sibling tools like skill_gap_analysis or career_path, and no prerequisites or exclusions are given.

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.