Skip to main content
Glama

Change Auto apply

update_auto_apply
Destructive

Turn Auto apply on or off, change its switches, and manage the résumés it uses. Actions: set, set_default_resume, set_resume_rules, add_resume, remove_resume, dismiss_suggestion. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "update_auto_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.
resume_idNoA résumé's id from get_auto_apply settings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "set",
      -  "set_default_resume",
      -  "set_resume_rules",
      -  "add_resume",
      -  "remove_resume",
      -  "help"
      -]New value: +[
      +  "set",
      +  "set_default_resume",
      +  "set_resume_rules",
      +  "add_resume",
      +  "remove_resume",
      +  "dismiss_suggestion",
      +  "help"
      +]
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the risk profile is conveyed structurally. The description adds that résumés can be attached and removed and that suggestions can be dismissed, which hints at side effects, but it never says what removal costs the user (lost auto-apply history, dependent applications) or that changes alter future automatic submissions. With annotations carrying the safety signal, a 3 is appropriate.

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?

Two sentences, front-loaded with the overall purpose followed by the action list and the help fallback — no padding. "Change its switches" is slightly vague phrasing but does not cost the reader much.

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

Completeness3/5

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

For a destructive, multi-action tool with a free-form nested params object and no output schema, the definition covers the what and the discovery mechanism but leaves gaps: return shape after each action, required vs optional fields per action, and error behavior are absent. Adequate, not complete.

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?

Schema coverage is 67% and the params object is free-form (additionalProperties: true), meaning the per-action fields exist only in the help response. The description compensates partially by pointing to action "help" for each action's fields, which is the right mitigation, but it conveys no semantics for params or resume_id beyond what the schema text already says.

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?

States the resource and intent directly ("Turn Auto apply on or off, change its switches, and manage the résumés it uses") and enumerates the six concrete actions, so an agent knows exactly what operation space this covers. It stops short of naming the get_auto_apply sibling as the read-only counterpart, so differentiation is implied by the update_ prefix and action list 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 Guidelines3/5

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

The action enumeration implies when each mode applies, and the "call with action help" instruction gives a discovery path, which is real guidance. However, there is no explicit rule about when to prefer get_auto_apply first, no prerequisites (e.g., does add_resume require the résumé to exist in Résumé Studio?), and no exclusions.

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.