Skip to main content
Glama
Sign In

GetMattered

by com.getmattered
OverviewDiscussionsAdmin

Update Auto Apply Settings

getmattered_update_automatic_apply_settings
DestructiveIdempotent

Turns Auto Apply on or off and sets its default mode, daily limit and lowest match. While on, applications start without asking per job. Turning it on needs the Hired Yesterday plan.

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

Input Schema

NameRequiredDescriptionDefault
enabledNotrue turns Auto Apply on, false turns it off. Left out, it stays as it is.
daily_limitNoMost applications Auto Apply starts in a day, 1 to 50. The plan's own daily cap can lower it. Left out, it stays as it is.
match_levelNoLowest match Auto Apply applies to: "excellent" (90+), "strong" (80+), "good" (70+) or "stretch" (60+). Left out, it stays as it is.
default_apply_modeNo"auto": applications go to the employer without asking first. "review": each one waits for the user's approval. Also the mode getmattered_apply uses when its mode is omitted. Left out, it stays as it is.

Output Schema

NameRequiredDescriptionDefault
changedYesThe settings this call asked to change.
settingsYesThe settings after the change. Null when the user declined the confirmation.
setupStepNoPresent while account setup is open: the first setup step.
notConfirmedYesTrue when the user declined the confirmation and nothing changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / setupStep / description
      Previous value: -"Set while account setup is open: the step to take first."New value: +"Present while account setup is open: the first setup step."
  2. Changed4 schema fields changed
    • changedInput schema / properties / daily_limit / description
      Previous value: -"Most applications Auto Apply starts in a day, 1 to 50. The plan's own daily cap can lower it. Omit to leave it as it is."New value: +"Most applications Auto Apply starts in a day, 1 to 50. The plan's own daily cap can lower it. Left out, it stays as it is."
    • changedInput schema / properties / default_apply_mode / description
      Previous value: -"\"auto\": applications go to the employer without asking first. \"review\": each one waits for the user's approval. Also the mode getmattered_apply uses when its mode is omitted. Omit to leave it as it is."New value: +"\"auto\": applications go to the employer without asking first. \"review\": each one waits for the user's approval. Also the mode getmattered_apply uses when its mode is omitted. Left out, it stays as it is."
    • changedInput schema / properties / enabled / description
      Previous value: -"true turns Auto Apply on, false turns it off. Omit to leave it as it is."New value: +"true turns Auto Apply on, false turns it off. Left out, it stays as it is."
    • changedInput schema / properties / match_level / description
      Previous value: -"Lowest match Auto Apply applies to: \"excellent\" (90+), \"strong\" (80+), \"good\" (70+) or \"stretch\" (60+). Omit to leave it as it is."New value: +"Lowest match Auto Apply applies to: \"excellent\" (90+), \"strong\" (80+), \"good\" (70+) or \"stretch\" (60+). Left out, it stays as it is."
  3. Changed1 schema field changed
    • addedOutput schema / properties / setupStep
      Added value: +{
+  "description": "Set while account setup is open: the step to take first.",
+  "type": "string"
+}
  4. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond them: the consequence of enabling (applications submit without per-job confirmation) and a plan/entitlement requirement. It does not, however, disclose what turning it off does to already-queued applications or any rate/auth specifics, leaving a meaningful gap for a destructive mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the operational effect front-loaded and the prerequisite last; no filler, no restatement of the title.

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 the schema handles partial-update semantics. For a destructive mutation, only the effect of disabling on pending applications is left unstated, a small but real gap.

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 description coverage is 100% and every parameter already documents its enum values, ranges and the 'left out, it stays as it is' partial-update behavior. The description's paraphrase ('default mode, daily limit and lowest match') adds no meaning beyond that, so the baseline 3 applies.

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?

States a specific verb set (turn on/off, set) applied to a named resource (Auto Apply settings) and enumerates exactly which settings it governs: default mode, daily limit, lowest match. This is clearly distinct from siblings like getmattered_update_job_preferences or getmattered_update_application_profile.

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?

Gives clear context for use ('while on, applications start without asking per job') and a real prerequisite ('Turning it on needs the Hired Yesterday plan'), which tells the agent when the call will fail. It does not explicitly route to alternatives or say when not to use it, so it stops short of a 5.

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

All GetMattered toolsInspect
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