Skip to main content
Glama

Keyword gap

careergenius_keyword_gap
Read-onlyIdempotent

Lists the keywords a job posting asks for (named tools, products, credentials, plus any you supply) and which of them the resume shows or does not show. Deterministic, no AI. Not a score and not a prediction of screening or interview outcomes. Without a key: one of the conversation's 10 free keyword/PDF calls. job_url needs a key.

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": {
      "on_behalf_of": "<on_behalf_of>"
    },
    "name": "careergenius_keyword_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeNoStructured resume. Only what the person really has done: every output is checked against it.
job_urlNoA public job posting link (Greenhouse, Lever, Ashby, SmartRecruiters, Workday or a page with JobPosting data). Fetched by our job-import engine; private or internal addresses are refused.
keywordsNo
resume_textNo
on_behalf_ofYesRequired. You confirm a person asked for this, and the resume is theirs (or they are authorised to use it).
posting_textNoThe job posting text (preferred).
idempotency_keyNoOptional, keyed calls only (ignored without a key). Retrying with the same key returns the first answer and is not charged twice. Only when you send it, that answer (which can contain text taken from the resume) is kept for 24 hours so the retry can be replayed, then deleted. Without it nothing from the request is stored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, idempotentHint, openWorldHint=false), it discloses that the result is deterministic with no AI and explicitly disclaims screening/interview prediction — meaningful expectation-setting that prevents over-trust. It also adds access/metering context (free calls without a key, key required for job_url), which the annotations do not convey.

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?

Front-loaded with the purpose and output shape in the first sentence, followed by scope disclaimers and metering. A few clauses are telegraphic fragments ('Deterministic, no AI.' / 'job_url needs a key.') that read as appended constraints rather than flowing prose, but little is wasted.

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

Completeness4/5

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

With no output schema, the description does the right work by describing what the result contains (keywords present vs. absent from the resume). For a 7-parameter tool with a deeply nested resume object, however, it does not explain the resume/resume_text choice or the posting_text/job_url duality, which are the decisions an agent actually has to make.

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?

Schema coverage is 71%, so most fields are documented structurally; the description adds real meaning only for a few: 'keywords' is additive ('plus any you supply') and 'job_url' carries an access restriction ('needs a key'). It says nothing about the resume vs. resume_text tradeoff or when posting_text should be preferred over job_url, leaving the two largest input choices to inference.

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 gives a specific verb and resource ('Lists the job keywords a job posting asks for') and defines the output shape precisely: which keywords the resume shows or does not show, including caller-supplied ones. It also fences off adjacent interpretations ('not a score and not a prediction of screening or interview outcomes'), though it never names a sibling tool by name, so differentiation is by negation rather than explicit routing.

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?

Implicit usage is clear from the tool's purpose (compare a posting's required keywords against a resume), and it adds quota context ('one of the conversation's 10 free keyword/PDF calls') plus a precondition ('job_url needs a key'). It does not explicitly say when to reach for this versus careergenius_tailor_resume or interview_prep, so the agent must infer the boundary.

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.

Resources