Skip to main content
Glama

Get clearance to submit

freeapply_clear_to_submit

Check whether one job can be submitted now and issue a 15-minute clearance that enforces per-minute pace, daily caps, and auto-run Stop limits.

Instructions

Go-ahead for one submit after checking the pace, the user's limits and, in auto-run, the Stop button. Comes right before the submit; freeapply_update_job refuses applied without its clearance. Use: right before every submit, with job_id. Not early, not for a job you won't submit now: each clearance counts toward the per-minute pace at once. Behavior: at most 3 submits a minute (or the user's slower setting) and the user's daily cap. A clearance: one job, 15 minutes, used up when applied is recorded; asking again for the same job issues a new one; kept only while FreeApply runs. Parameters: job_id ties the clearance to that one job (without it you only see the pace). method: external (employer or ATS form, the default), easy_apply or email; the pace and daily cap count submits by that method, and easy_apply also needs one-click apply allowed in Settings. run_id, only in auto-run (from freeapply_manage_autorun start), adds the user's Stop and limits, and counts as the run checking in. Returns: {clear, advice, last_minute, limit_per_minute, today, daily_cap}, plus clearance {job_id, expires_at} when clear. clear false: don't submit; prepare the next job, call again later. refused: one-click apply is off; apply on the employer's site or skip the job. stop_run true (with reason): the run must end now: freeapply_manage_autorun action finish. restart true: the user saved new settings and wants them used now: submit and record this job, start no other, finish the run; the next begins at once.

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

Input Schema

NameRequiredDescriptionDefault
job_idNoThe job about to be submitted.
methodNoHow you will submit (default external).
run_idNoAuto-run only: the run_id from freeapply_manage_autorun start.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.6
    • changedInput schema / properties / job_id / description
      Previous value: -"The job about to be submitted; without it you only see the pace."New value: +"The job about to be submitted."
    • changedInput schema / properties / method / description
      Previous value: -"How you will submit: external (employer or ATS form; default), easy_apply (a job board's one-click apply; refused while one-click apply is off) or email."New value: +"How you will submit (default external)."
    • changedInput schema / properties / run_id / description
      Previous value: -"Unattended run only: the run_id from freeapply_autorun start; first checks that run's limits and the dashboard's Stop button, and keeps the run alive."New value: +"Auto-run only: the run_id from freeapply_manage_autorun start."
  2. Changed1 schema field changedv1.0.5
    • changedInput schema / properties / run_id / description
      Previous value: -"Unattended run only: the run_id from freeapply_autorun start; first checks that run's time and application budgets and the dashboard's Stop button."New value: +"Unattended run only: the run_id from freeapply_autorun start; first checks that run's limits and the dashboard's Stop button, and keeps the run alive."
  3. Changed3 schema fields changedv1.0.4
    • changedInput schema / properties / job_id / description
      Previous value: -"The job about to be submitted."New value: +"The job about to be submitted; without it you only see the pace."
    • changedInput schema / properties / method / description
      Previous value: -"How you will submit: external (an employer or ATS form; default), easy_apply (a job board's one-click apply) or email."New value: +"How you will submit: external (employer or ATS form; default), easy_apply (a job board's one-click apply; refused while one-click apply is off) or email."
    • changedInput schema / properties / run_id / description
      Previous value: -"In an unattended run only: the run_id that freeapply_autorun start returned."New value: +"Unattended run only: the run_id from freeapply_autorun start; first checks that run's time and application budgets and the dashboard's Stop button."
  4. Addedv1.0.2

TDQS

A4.9/5.0
Behavior5/5

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

With annotations already declaring non-read-only, non-idempotent, and non-destructive behavior, the description adds substantial stateful context: rate limits, daily caps, 15-minute clearance expiry, one-job scope, method-specific counting, and auto-run Stop/restart semantics. These details go well beyond what the annotations provide.

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 dense and well-structured with Use, Behavior, Parameters, and Returns sections, and the core purpose is front-loaded. It is somewhat long and repeats the 'right before submit' timing in the opening and Use section, but the length is largely justified by the tool's stateful complexity.

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?

For a complex, non-idempotent stateful tool with no output schema, the description is complete enough: it explains preconditions, rate limits, parameter effects, return fields, and how to react to clear=false, refused, stop_run, and restart outcomes.

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 100%, but the description still adds meaningful semantics: job_id ties clearance to one job and without it only pace is visible; method affects pace/daily cap and easy_apply requires one-click apply enabled; run_id only applies in auto-run and activates Stop/limits and run check-in 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 action and resource: a go-ahead/clearance for one submit, checked against pace, user limits, and auto-run Stop state. It also distinguishes itself from freeapply_update_job by noting that job update refuses 'applied' without this clearance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives explicit timing and exclusions: use right before every submit, with job_id, not early, and not for a job that will not be submitted now. It also routes stop_run handling to freeapply_manage_autorun action finish.

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