Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Plan my career path

career_path
Read-onlyIdempotent

Create a practical career path from verified candidate experience, education and skills.

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": "career_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetRoleNo
horizonMonthsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description adds only that inputs are 'verified' profile data; it does not say whether the generated plan is persisted anywhere, what form the plan takes, or how the horizon affects output — and with readOnlyHint=true against the verb 'Create', an agent could misread this as a write operation.

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 front-loaded sentence with no filler. It is efficient, but its brevity is also the source of the missing guidance rather than evidence of tight curation.

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?

This is a generative tool with no output schema and zero parameter documentation, so the description carries the full burden of explaining the shape of the returned plan — and it does not. For a tool whose whole value is the produced artifact, saying nothing about the result leaves a significant gap.

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 both parameters. The description never mentions targetRole or horizonMonths (including its 3-60 month bounds and the fact that neither parameter is required), so it does not compensate for the schema gap; defaults and units are undocumented.

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 pairs a specific verb with a specific resource ('Create a practical career path') and names the inputs it derives from (verified candidate experience, education, skills). It is clearly distinguishable from adjacent tools like skill_gap_analysis or job_match_score in intent, though it never explicitly contrasts itself with those siblings.

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 prerequisites, and no mention of alternatives such as skill_gap_analysis or profile_strength. The agent is left to infer entirely from the name when this planning tool is the right call versus a narrower analysis tool.

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.