Democruit

Apply resume fixes

fix_resume

Destructive

Apply fixes supported by a saved ATS report to the resume. Requires conversation confirmation. Operations: fix. Returns the response envelope; nextActions list what the user can do next, primary first. Use confirm: false for a preview, then repeat identical inputs with confirm: true and the preview confirmationToken after the user confirms.

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": {
      "operation": "<operation>",
      "confirm": "<confirm>"
    },
    "name": "fix_resume"
  }
}

Input Schema

Name	Required	Description
`confirm`	Yes	Set to true only after the user has explicitly confirmed this action in the conversation. Describe what will change to the user first.
`reportId`	No	Optional when exactly one candidate item exists: omit its ID to use that item. Ask which saved item to use only when several exist.
`operation`	Yes	Choose the task. Each operation accepts only its own fields.
`issueTypes`	No	The issue types supplied by the user. Follow the type and allowed values in this schema.
`shortReason`	No	The short reason supplied by the user. Follow the type and allowed values in this schema.
`criterionKey`	No	The criterion key supplied by the user. Follow the type and allowed values in this schema.
`saveSequence`	No	Optional. Omit to let the server use the latest saved version. Supply it only as the sequence you last read, to detect concurrent edits; do not ask the user unless they request this setting.
`sourceIssueKey`	No	The source issue key supplied by the user. Follow the type and allowed values in this schema.
`confirmationToken`	No	Token returned by the preview. Send it unchanged with confirm: true; it is valid for 15 minutes and only for the previewed inputs.
`evidenceReferences`	No	The evidence references supplied by the user. Follow the type and allowed values in this schema.

Output Schema

Name	Required	Description	Default
`data`	No
`page`	No
`error`	No
`links`	No
`status`	Yes
`notices`	No
`polling`	No
`summary`	Yes
`agentHint`	No
`nextActions`	Yes
`appliedDefaults`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 8, 2026

removedInput schema / allOf

Removed value: -[
-  {
-    "if": {
-      "properties": {
-        "operation": {
-          "enum": [
-            "fix"
-          ]
-        }
-      },
-      "required": [
-        "operation"
-      ]
-    },
-    "then": {
-      "required": [
-        "confirm"
-      ]
-    }
-  }
-]

addedInput schema / properties / confirmationToken

Added value: +{
+  "description": "Token returned by the preview. Send it unchanged with confirm: true; it is valid for 15 minutes and only for the previewed inputs.",
+  "maxLength": 200,
+  "type": "string"
+}

changedInput schema / properties / saveSequence / description

Previous value: -"Optional. Omit to use the current saved document sequence; do not ask the user unless they request this setting."New value: +"Optional. Omit to let the server use the latest saved version. Supply it only as the sequence you last read, to detect concurrent edits; do not ask the user unless they request this setting."

AddedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. Beyond that, the description discloses the two-phase preview-then-commit workflow, the conversation-confirmation prerequisite, and that the response envelope's nextActions is primary-first — real behavioral detail not derivable from annotations.

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 description is front-loaded with purpose, then workflow, with no filler. The phrase "Operations: fix." is redundant since the operation enum has exactly one value, a small waste in an otherwise tight definition.

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?

An output schema exists, so return values need no elaboration, yet the description still notes the envelope and nextActions ordering. Combined with the confirmation workflow, token reuse, and preview semantics, an agent has everything needed to call this destructive tool safely.

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?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema by tying confirm to the preview/commit pair and requiring the confirmationToken be sent with identical inputs. That relationship between two parameters is not spelled out in either field's schema description.

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?

"Apply fixes supported by a saved ATS report to the resume" gives a specific verb (apply), resource (resume), and source constraint (saved ATS report), which separates it from analysis-only siblings like check_resume. It does not name any sibling explicitly, so differentiation is implied rather than stated.

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 gives a concrete operating procedure: preview with confirm: false, then repeat identical inputs with confirm: true plus the preview token after the user confirms. It does not exclude alternatives (e.g., when to prefer check_resume first or restore_resume_version for undo), but the when-to-use context is clear.

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

All Democruit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?