Skip to main content
Glama

Read job search status

get_radar_status
Read-only

State of the user's job radar: how many matches are in the working list, still waiting in the pool, saved, deferred or in the Skipped pile ('archived' counts what was skipped and what was put away); when a scan last brought something in; whether the daily automatic search is switched on; and the explicit search filters, if the user set any — the progress picture without paging through every match. last_scan_at moves when new vacancies arrive, so a scan that found nothing new leaves it unchanged. search_query is what the last scan actually searched for (role, place, country) — the role there came from the filters, career memory or the resume, so an empty filters.role does not mean the radar searched for no role; search_query.role is the title the boards were searched with and search_query.role_display the same role in the user's own words, as typed in the filters; search_role is what the next scan searches for (null: nothing names a role yet). next_scan_at is set only on the free plan while its one scan a week is spent. All zeros with auto_search_enabled=false is the normal answer for someone who has never used the radar.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
savedNo
activeYesMatches in the working list right now (new plus saved).
filtersNoExplicit search filters, when the user set any. They outrank the resume.
archivedNo
deferredNo
search_roleNoThe title the next scan searches for: the role from the filters, career memory or the resume, spelled the way job boards spell it once a scan has derived the search profile for this resume and role; before that, the role as set. Null means nothing names a role — a scan would fail with role_unknown until the user gives one.
last_scan_atNoISO timestamp of the most recent match found by a scan; null if the radar never ran.
next_scan_atNoFree plan only, while its one scan a week is spent: ISO timestamp of when the next scan becomes available. Null when a scan is available now or the plan is paid (a paid plan's scans come back the next day).
search_queryNoWhat the last scan actually searched for — the role, place and country the radar settled on from filters, career memory, the resume and, when nothing else named one, the country the user signed up from. Null before the first scan. It stays after the filters or the resume change until the next scan, so it can differ from filters and search_role, which is what the next scan will run. The role here is what the scan searched for even when filters.role is empty.
pool_remainingYesFound but not yet shown to the user — what a fresh look would reveal.
auto_search_enabledYesWhether the daily automatic scan and its digest are on for this user.
search_paused_untilNoISO timestamp the user's search pause ends, null when there is none. While paused, nothing the product starts on its own reaches them and the daily scan does not run. set_search_pause with months=null lifts it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / $defs / RadarFiltersItem / properties / excluded_countries
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Countries a search open to any country leaves out (ISO codes).",
      +  "title": "Excluded Countries"
      +}
    • addedOutput schema / $defs / RadarFiltersItem / properties / excluded_locations
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Cities a search of a whole country leaves out; remote jobs there stay.",
      +  "title": "Excluded Locations"
      +}
  2. Changed3 schema fields changed
    • addedOutput schema / $defs / RadarSearchQueryItem / properties / role / description
      Added value: +"The title the boards were searched with. Once a scan has derived the search profile it is the English spelling job boards use, so it can differ from the words the user typed."
    • addedOutput schema / $defs / RadarSearchQueryItem / properties / role_display
      Added value: +{
      +  "description": "The same role in the user's own words: filters.role as typed when the last scan ran those filters, otherwise the searched title. This is the name the user knows the role by.",
      +  "title": "Role Display",
      +  "type": "string"
      +}
    • changedOutput schema / $defs / RadarSearchQueryItem / required
      Previous value: -[
      -  "role"
      -]New value: +[
      +  "role",
      +  "role_display"
      +]
  3. Changed3 schema fields changed
    • addedOutput schema / $defs / RadarLocalBoardItem
      Added value: +{
      +  "properties": {
      +    "name": {
      +      "title": "Name",
      +      "type": "string"
      +    },
      +    "url": {
      +      "title": "Url",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "url"
      +  ],
      +  "title": "RadarLocalBoardItem",
      +  "type": "object"
      +}
    • addedOutput schema / $defs / RadarSearchQueryItem / properties / found
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Matches the last scan kept under the filters; null while it runs and on scans before 2026-09-27.",
      +  "title": "Found"
      +}
    • addedOutput schema / $defs / RadarSearchQueryItem / properties / local_board
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/RadarLocalBoardItem"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "In countries whose postings live mostly on a local job site the radar does not search (Kazakhstan, Ukraine, Turkey, Korea, Georgia, the Gulf and others): that site's name and its search for the role. The radar never reads it; null for every other country."
      +}
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only tell us it is a safe read; the description adds non-obvious semantics: last_scan_at is unchanged when a scan finds nothing, next_scan_at is set only on the free plan while its weekly scan is spent, search_role is null when no role is named yet, and all-zeros with auto_search_enabled=false is the normal new-user answer. That is substantial context beyond the readOnlyHint.

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?

The content is front-loaded with the purpose and then layers field clarifications; nearly every clause earns its place by preventing a misread (empty filters.role, unchanged last_scan_at). It is dense and em-dash-heavy, which makes it harder to scan than a short bulleted structure would be.

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 an output schema present, the description need not restate return values, yet it supplies exactly the interpretive gaps the schema cannot (why last_scan_at looks stale, why filters.role can be empty, free-plan next_scan_at). The only meaningful omission is explicit sibling routing, which is only implied.

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?

There are zero input parameters, so the baseline is 4. The description does not need to explain inputs, and its field-level discussion (filters.role vs search_query.role vs search_role, role_display) adds interpretive value even though the output schema already documents the fields.

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?

The opening clause names a specific resource and scope ('State of the user's job radar') and enumerates exactly what is reported: match counts by stage, last scan time, auto-search flag, and active filters. The phrase 'the progress picture without paging through every match' implicitly separates it from the match-listing sibling get_radar_matches.

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

Usage Guidelines4/5

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

The description makes clear this is the summary/overview call ('the progress picture without paging through every match'), which points an agent away from get_radar_matches for status checks. It stops short of naming alternatives explicitly or saying when not to use it, but the implied routing is strong.

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.