Skip to main content
Glama

Worklittle Jobs

Jobs · Update Apply Settings

update_apply_settings
Idempotent

Jobs — Change how Worklittle applies for the user. Use when they ask Worklittle to apply to matching jobs on its own, to send applications without stopping for their review, or to tailor their resume to each job (or to stop any of these). Only send the settings to change.

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

Input Schema

NameRequiredDescriptionDefault
auto_applyNoWorklittle applies to jobs that match the user on its own.
auto_submitNoSend applications without stopping for the user's review first.
tailor_resumeNoTailor the user's resume to each job it applies to.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / auto_apply / description
      Added value: +"Worklittle applies to jobs that match the user on its own."
    • addedInput schema / properties / auto_submit / description
      Added value: +"Send applications without stopping for the user's review first."
    • addedInput schema / properties / tailor_resume / description
      Added value: +"Tailor the user's resume to each job it applies to."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description's genuine addition is 'Only send the settings to change,' which discloses partial-update semantics — important given zero required parameters. That is useful but modest context beyond the annotations, and nothing is said about what an empty call does.

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 purpose followed by usage triggers, with no filler. The parenthetical 'or to stop any of these' is doing real work by covering the false case efficiently.

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?

An output schema exists, so return values need no explanation, and annotations cover safety and idempotency. For a three-optional-boolean partial-update tool the description is essentially sufficient; only the no-op/empty-payload behavior is left implicit.

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 100% and each boolean already carries its own description, so the description adds little field-level detail. Its paraphrase of the three settings duplicates the schema, and only the partial-update instruction ('Only send the settings to change') adds meaning the schema lacks. Baseline 3 is appropriate.

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?

The description names a specific verb-plus-resource combination — 'Change how Worklittle applies for the user' — and enumerates the three settings domains it governs (auto-apply, auto-submit, resume tailoring). It reads clearly as the mutation counterpart to get_apply_settings, though it never names that sibling explicitly.

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 gives concrete user-intent triggers: when the user asks Worklittle to apply on its own, to send applications without review, or to tailor the resume, plus the explicit 'or to stop any of these' case. It stops short of naming the read tool to consult first or any prerequisites, so it is clear context without 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.

Resources