ResumeQuick

Check a background task

get_task_status

Read-only

Report a background task by the task_id a tool returned (create_profile, translate_resume, request_resume_update, export_resume_pdf, start_radar_scan, apply_vacancy_resume_suggestions, generate_cover_letter and the analyze_* tools): status processing | completed | failed | cancelled, progress, on failure the reason, and on success what it produced — the new resume's resume_id, the translated copy's resume_id, the resume_id a rewrite changed (get_resume reads it) and the sections it kept as they were (guarded_sections), whether the PDF is ready, how many postings a scan found, the app_url of a written cover letter. Returns 'not_found' if the task does not exist or does not belong to the current user.

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description
`type`	Yes	What the task does, e.g. 'resume_translation', 'resume_update', 'pdf_generation', 'radar_scan', 'apply_suggestions', 'vacancy_analysis', 'resume_suggestions', 'cover_letter_generation', 'offer_analysis'.
`error`	No	Set when status is 'failed'.
`result`	No	Set when status is 'completed'.
`status`	Yes	'processing' covers a task waiting in the queue and one running.
`task_id`	Yes
`progress`	No	0–100 while it runs, when the task reports it.
`created_at`	Yes	When the task was started, ISO 8601.
`completed_at`	No	When it finished or failed, ISO 8601.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

addedOutput schema / $defs / TaskResult / properties / guarded_sections

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "For a rewrite: sections (by section name, e.g. 'summary', 'experience') the rewrite came back with empty or with fewer entries although the request was not read as a removal, so their previous content was kept. update_resume_section clears or trims a section directly.",
+  "title": "Guarded Sections"
+}

Changed1 schema field changedOct 25, 2026

addedOutput schema / $defs / TaskResult / properties / unchanged_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Suggestions that changed nothing: the resume states nothing they build on.",
+  "title": "Unchanged Count"
+}

Changed3 schema fields changedOct 17, 2026

addedOutput schema / $defs / TaskResult / properties / best_company

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Company of that strongest new posting.",
+  "title": "Best Company"
+}

addedOutput schema / $defs / TaskResult / properties / best_match_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The strongest of the postings this scan found new: its radar match id.",
+  "title": "Best Match Id"
+}

addedOutput schema / $defs / TaskResult / properties / best_title

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Job title of that strongest new posting.",
+  "title": "Best Title"
+}

First observedOct 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already establish read-only, non-destructive, closed-world behavior. The description adds substantial behavioral detail: statuses, progress, failure reasons, success artifacts mapped to task types, and a not_found result for missing or unauthorized tasks.

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 purpose is front-loaded and the definition is information-dense with little waste. However, it is a single very long sentence with a large parenthetical list and many semicolon-like clauses, making it harder to scan than it could be.

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?

Given the simple one-parameter input, existing output schema, and read-only annotations, the description provides all the context an agent needs. It covers valid sources of task_id, lifecycle states, failure behavior, success outputs by task type, and missing/unauthorized behavior.

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

Parameters5/5

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

Schema coverage is low, so the description has to compensate for the single task_id parameter. It does so by explaining that task_id is the value returned by specific background tools and by tying that parameter to the not_found ownership behavior.

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 description states a specific verb and resource: report a background task by task_id. It distinguishes this tool from siblings by naming the producer tools whose task_ids it tracks and by explaining the status/progress/result information returned.

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?

It clearly says to use the task_id returned by a tool that runs in the background and lists many such tools. It does not explicitly state when not to use it or name alternative status-checking tools, but the surrounding context makes its role clear.

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

All ResumeQuick tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.