Skip to main content
Glama

Search job boards now

start_radar_scan
Idempotent

Start a job radar scan: search job boards for vacancies matching the user's active resume. Runs asynchronously — returns a task_id immediately; the scan takes up to a minute, then get_radar_matches shows the results and get_radar_status.last_scan_at says whether it brought anything in (a scan that found nothing new leaves it as it was); get_task_status(task_id) reports progress and the outcome. Calling it while a scan is already running returns the same task_id (no double scan). Consumes one radar scan from the user's plan quota — several a day on a paid plan, one a week on the free plan, where the morning's automatic scan counts too; the account's first scan ever is not counted, and neither is a scan with changed filters after one that found nothing, while the account has never had a match. Returns 'no_resume' when the account has neither a resume nor a role named at setup, 'role_unknown' when nothing names the role to search for (no role in the radar filters or career memory, no title, position or skills on the resume; set_radar_filters stores a role), and 'limit_exceeded' when the quota is spent, naming the day it frees up. The same search as the last scan (same role, place and filters on the same resume) within an hour of it starts nothing and spends nothing: it returns 'recent_scan' with the minutes since that scan and when the same search can run again; a search with other filters (set_radar_filters) starts at once.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
statusNoprocessing
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safety profile (non-read-only, open-world, idempotent, non-destructive); the description adds substantial context beyond that: asynchronous execution with an immediate task_id, up to a minute duration, quota consumption rules with plan-tier specifics and exemptions, and the exact error strings 'no_resume', 'role_unknown' and 'limit_exceeded' with their triggers. It also explains the one-hour duplicate-search window and that it starts and spends nothing, which deepens the idempotency hint rather than repeating it.

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 purpose, async behavior and result routing before the operational caveats, and nearly every clause carries decision-relevant information. The quota sentence, however, stacks plan tiers, exemptions and a conditional into one long chained clause that is hard to parse on first read and could be broken into shorter statements.

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 zero-parameter, quota-consuming, asynchronous action this covers everything an agent needs: immediate return value, where results surface later, how to poll, side effects on quota, dedup behavior and all named error outcomes. An output schema exists, so return-shape detail is appropriately delegated rather than restated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4. The description correctly implies the search scope comes entirely from stored state (active resume, radar filters, career memory) rather than arguments, which is the only parameter-relevant fact an agent needs here.

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?

Opens with a specific verb and resource ('Start a job radar scan: search job boards for vacancies matching the user's active resume') and immediately distinguishes itself from get_radar_matches, get_radar_status and get_task_status by assigning each of those the results/progress role. An agent knows exactly what this tool does and what it does not do.

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?

Explicit about when to call (need fresh matches from job boards), when not to (a scan is already running returns the same task_id; an identical search within an hour returns 'recent_scan'), and which sibling to use instead for results (get_radar_matches), status (get_radar_status.last_scan_at) and progress (get_task_status). It also names set_radar_filters as the way to change the search, which is the correct alternative action.

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.