Skip to main content
Glama

TrueInterview

Save my application answers

update_application_answers
Idempotent

Save answers application forms ask that a résumé does not state, so the candidate is asked once: their postal address (county included), the phone number forms get, citizenships, where they may work (per country: legally authorized, sponsorship needed now or later, and optionally the basis, visa type and status), relocation, office work, start date, notice period, accommodations, clearance, a salary range and history, date of birth and profile links, and how they want their agent to apply (résumé tailoring, cover letters, reviewing the first tailored résumé, and answer_mode: full_auto has their agent answer everything it can work out; save it only once they agreed to the full-automation sentence prepare_application gives you, which this server cannot check). get_application_checklist's setup lists what is still missing, with the questions to ask word for word and what the résumé already says (setup.prefill): a yes to a pre-filled value is their answer. Save what the candidate tells you in this conversation, in their words, as they say it (during an application too), and say in one line what you saved: no need to ask first. The answer carries setup as it now stands; setup.complete true means the setup is done. With no profile yet, this starts one. Never guess an answer. Self-identification questions (gender, ethnicity, veteran status, disability) are never saved: only whether to ask each time or always decline. A bank card or government ID number, a password or a token is refused and nothing is saved. A field you leave out is untouched, null removes an optional one, and a list you send replaces the saved list. get_application_checklist and prepare_application read what is saved.

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_application_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
phoneNoThe number forms get, with its country code. Without one, forms use the résumé's. null removes it.
stateNoState, province or region. null removes it, for a country that has none.
countyNoCounty or district, when forms ask for it. null removes it.
countryNoThe country they live in.
in_personNoOpen to in-person work.
us_personNoA "U.S. person" under export-control rules (ITAR/EAR): a U.S. citizen, permanent resident, refugee or asylee. Only their own answer.
github_urlNonull removes it.
salary_maxNoPer year.
salary_minNoPer year.
answer_modeNoHow far their agent answers forms without them: ask_when_unsure (default) asks once about what only they know; full_auto answers everything that can honestly be worked out. Save full_auto only after the candidate agreed to the setup's FULL_AUTO_ATTESTATION, read to them word for word (prepare_application's steps carry it). A right to work, a citizenship, a self-identification answer, a criminal record and a legal waiver are never inferred either way.
postal_codeNonull removes it, for a country that has none.
submit_modeNoKept from an earlier setup and changes nothing: the candidate fills in and submits every form themselves (2026-11-19).
citizenshipsNoCountries of citizenship. Replaces the saved list; [] clears it.
cover_letterNoWhen to write a cover letter: when_asked (default, when the form asks for one), always or never.
linkedin_urlNonull removes it.
address_line1No
address_line2NoApartment or suite. null removes it.
date_of_birthNoYYYY-MM-DD.
notice_periodNoe.g. "2 weeks", "available now".
portfolio_urlNoA personal website or portfolio. null removes it.
accommodationsNoNeed workplace accommodations (disability, religious or other)? prefer_not is kept as its own answer.
salary_historyNoPast base salaries, most recent first. Replaces the saved list.
salary_currencyNoISO code, e.g. "USD".
active_clearanceNoHolds an active government security clearance.
resume_tailoringNoHow far tailor_resume may change the résumé for each job: off (send it as saved), keywords (default) or rewrite. Pass it as tailor_resume's intensity.
work_eligibilityNoEvery country they would take a job in, each with both answers. Replaces the saved list; the United States entry also sets work_authorized_us and requires_sponsorship.
work_authorized_usNo
earliest_start_dateNoA date (YYYY-MM-DD) or words, e.g. "2 weeks after an offer".
review_first_resumeNoShow the candidate the tailored résumé of their first application before it is used.
willing_to_relocateNo
requires_sponsorshipNoNow or in the future, for an employment visa.
voluntary_disclosuresNoHow voluntary self-identification questions are handled: ask_each_time (default) or always_decline ("Decline to self-identify"). No answer to one is ever saved.
foreign_government_tiesNoFamily or other ties to a foreign government that employers must ask about.
reliable_transportationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses that a missing profile is started, omitted fields are untouched, null removes optional fields, lists replace saved lists, and full_auto requires the candidate's agreement to the attestation. It also explains refusal behavior and that the response carries setup as it now stands, with setup.complete indicating completion.

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

Conciseness3/5

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

The description is front-loaded and information-dense for a 35-parameter tool, but it is delivered as a single long run-on paragraph with deeply nested clauses. It could be reorganized into clearer sections or bullets to make the rules easier to scan and apply.

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 35-parameter mutation with no output schema, it covers persistence rules, the setup-complete return signal, prerequisites for full_auto, refusal cases, and the relationship to get_application_checklist and prepare_application. Nothing essential for correct invocation appears missing.

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 description coverage is high at 86%, so per-field meaning is largely handled by the schema. The description still adds value by explaining cross-cutting semantics for omitted/null/list fields, the attestation prerequisite for answer_mode, and that submit_mode is deprecated and changes nothing.

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 first sentence names the action ('Save answers') and the resource ('application forms ask that a résumé does not state'), then enumerates the scope of saved profile data. The closing sentence distinguishes it from read-oriented siblings by saying get_application_checklist and prepare_application read what is saved.

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 explicit invocation context: save what the candidate tells you in this conversation, no need to ask first, and use get_application_checklist's setup to see what is still missing. It also states clear prohibitions against guessing and against saving self-identification answers or secrets, though it does not name alternatives for overlapping update tools.

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