Skip to main content
Glama

Analyze a job match

analyze_radar_match

Analyze one radar match (by match id) against the user's resume, using the posting text the radar already stored; it does not fetch the job page. Some boards hand over only a teaser (under 400 characters): such a match is not analyzed and spends nothing; it is put in the tracker unanalyzed and comes back with status='needs_full_posting'; analyze_tracked_vacancy with the full posting text as 'description' analyzes it. Otherwise consumes one vacancy analysis from the user's quota per match. Runs asynchronously: get_vacancy_detail(analysis_id) shows the result in a few seconds. If this match was already analyzed the existing analysis is returned with reused=true and nothing is spent. Returns 'limit_exceeded' naming the day it frees up when the quota is gone, 'posting_closed' when the job board says the posting is gone (closed_at is set; the match is put away and nothing is spent), 'no_resume' when the account has no resume yet (nothing is spent), and 'not_found' if the match does not belong to the current user.

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": {
      "input": "<input>"
    },
    "name": "analyze_radar_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
reusedNo
statusYes'processing' — a new analysis was enqueued and a credit spent; 'reused' — this match was already analyzed; 'needs_full_posting' — the board gave only a teaser, so nothing was analyzed or spent and the match sits in the tracker unanalyzed under analysis_id until the full text is added.
task_idNoBackground job id; null when an existing analysis was reused.
match_idYes
analysis_idYesPass to get_vacancy_detail to read the result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Far exceeds the annotations: discloses quota consumption per match, asynchronous execution with results in a few seconds, zero spend on teaser postings, closed postings, missing resumes, and re-analysis of an already-analyzed match (reused=true), plus the named error outcomes limit_exceeded, posting_closed, no_resume, and not_found. The reuse-on-repeat statement sits in mild tension with idempotentHint=false, but that hint is defensible because the first call does mutate quota and tracker state, so this is not a contradiction.

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 core action and scope, then proceeds through the teaser exception, quota, async, and error cases in a logical order. It is dense and somewhat run-on in the error enumeration, but nearly every clause carries operational information.

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

Completeness5/5

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

For a tool that spends quota and runs asynchronously, the description covers cost, timing, reuse, and every failure mode an agent must branch on. An output schema exists, yet the status codes are still called out, which is exactly what an agent needs to decide its next step.

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?

Only one parameter and no schema description coverage, so the description carries the burden; it clarifies that the id identifies a radar match and implies provenance from the radar listing. It does not describe the id's format or how to obtain one beyond naming get_radar_matches, so the added meaning is modest but adequate for a single-field input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

States a specific verb and resource: analyze one radar match by match id against the user's resume using the stored posting text. It also explicitly demarcates what it does not do ('it does not fetch the job page'), separating it from any fetch-based sibling.

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

Usage Guidelines5/5

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

Gives explicit when-to-use and when-not conditions: teaser-only matches (under 400 characters) are not analyzable here and should be routed to analyze_tracked_vacancy with the full posting text as 'description'. It also points to get_vacancy_detail(analysis_id) for results and get_radar_matches for the match id.

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.