Skip to main content
Glama

VeritaHire live jobs

Save an answer the person gave

save_answer
Idempotent

For a connected person: saves their answer to one application question (key from get_my_gaps or get_my_answers), with persons_words = what they actually said, so no form ever has to ask them again. Per-job questions need job exactly as get_my_answers shows it. Only answers the person gave - never a guess. Legal history, pay history, date of birth and licence numbers are not kept.

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": {
      "key": "<key>",
      "answer": "<answer>",
      "persons_words": "<persons_words>"
    },
    "name": "save_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNoFor per-job questions: the job as get_my_answers shows it
keyYes
answerYesThe answer as forms should get it
access_tokenNoNot needed when the person signed in through your Connect / sign-in button (OAuth). Otherwise the access_token from finish_connecting.
persons_wordsYesWhat the person said or typed, verbatim

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / access_token / description
      Previous value: -"From finish_connecting"New value: +"Not needed when the person signed in through your Connect / sign-in button (OAuth). Otherwise the access_token from finish_connecting."
    • changedInput schema / required
      Previous value: -[
      -  "access_token",
      -  "key",
      -  "answer",
      -  "persons_words"
      -]New value: +[
      +  "key",
      +  "answer",
      +  "persons_words"
      +]
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses which categories of data are deliberately not persisted (legal history, pay history, date of birth, licence numbers) and enforces a verbatim-source rule that no structured field states. The idempotent and non-destructive hints cover the write profile, so the description's added value is retention policy and attribution semantics.

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?

Front-loaded with the core action and dense with useful constraints, with no filler sentence. The opening clause chain is slightly run-on, but every clause carries distinct information.

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?

For a non-destructive, idempotent write with no output schema, the description covers key provenance, verbatim-source discipline, retention exclusions and the per-job conditional. It does not say what happens on an unknown or stale key, which is the main residual gap.

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 coverage is 80%, so the baseline would be 3; the description earns above that by explaining that `key` comes from get_my_gaps/get_my_answers (that parameter has no schema description at all) and that `persons_words` means what the person actually said, not a paraphrase. The `job` field's required format is also clarified beyond the schema's wording.

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 and resource — saves one answer to one application question for a connected person — and anchors the `key` parameter's provenance in the sibling read tools (get_my_gaps or get_my_answers). An agent can immediately tell this apart from the retrieval siblings without opening any schema.

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 preconditions: the person must be connected, per-job questions require `job` in exactly the form get_my_answers shows, and only person-supplied answers may be saved ('never a guess'). It names the source tools for keys but does not spell out explicit exclusions or a when-not-to-use path, so it falls just short of 5.

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