Skip to main content
Glama

analyze_job_match

Compare a saved resume with a job description to assess match quality and reveal gaps, helping you tailor your application.

Instructions

Get a prompt to analyze how well your saved resume matches a job description

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": {
      "jobDescription": "<jobDescription>"
    },
    "name": "analyze_job_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobDescriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden, and it does disclose the key behavioral trait that the output is a prompt rather than an analysis. It also implies a dependency on the stored resume ('your saved resume'). However, it says nothing about what the returned prompt looks like, whether the caller is expected to execute it, or any prerequisite such as having run save_resume first.

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 well-formed sentence with no filler, and the core purpose is front-loaded. It could be marginally sharper by leading with the analysis goal rather than 'Get a prompt', but nothing is wasted.

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?

For a one-parameter tool with no annotations and no output schema, the definition covers the essentials but omits two things that matter in this prompt-returning pattern: that a resume must already be saved, and that the returned prompt still needs to be run against a model. Otherwise it is self-contained.

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?

There is one required parameter with 0% schema description coverage, so the schema provides no semantics at all. The description partially compensates by identifying the input as a job description, but it does not clarify whether that is raw posting text, a URL, or an ID, leaving the agent to guess the expected format.

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 states a specific verb-plus-resource ('Get a prompt to analyze how well your saved resume matches a job description') and implicitly scopes it against siblings like get_cover_letter_prompt and get_resume_tailoring_prompt by naming the match-analysis task. It is clear what the tool produces, though it never explicitly names an alternative or boundary.

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 for evaluating fit between the saved resume and a posting. There is no explicit when-to-use guidance, no mention that a resume must be saved first, and no stated condition pointing to a sibling prompt tool instead.

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