Skip to main content
Glama

Change or forget a saved application answer

editApplicationAnswer
DestructiveIdempotent

Change the answer auto-apply reuses for one employer question, or forget it so the next form asking it waits for the candidate. Take question exactly from readApplicationAnswers. A later real answer to the same question replaces this edit. Only change what the candidate asked to change, in their words.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "question": "<question>",
      "answer": "<answer>"
    },
    "name": "editApplicationAnswer"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerYesThe new answer in the candidate's words; null forgets the remembered answer.
questionYesThe question exactly as readApplicationAnswers lists it.

Output Schema

NameRequiredDescriptionDefault
defaultsYes
rememberedYes
missingBasicsYes
postalAddressYes
selfIdentificationYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false. The description adds real context beyond that: what forgetting does downstream (the next form waits for the candidate), that edits are provisional and can be overwritten by a genuine answer, and that inputs and results are privately recorded. The last point is boilerplate-ish but is a disclosure the annotations do not carry.

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 core action and the readApplicationAnswers dependency are front-loaded, and each operating sentence carries a distinct constraint. The trailing privacy/telemetry sentence is generic and could be trimmed, but it is short and clearly separated.

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?

Two fully documented required parameters, complete type/null semantics, an output schema that removes the need to describe return values, and annotations covering the safety profile. The description supplies the missing pieces: the read-then-edit workflow and the supersession behavior. Only a note on permission or failure conditions is absent.

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 both parameters already document that question must match readApplicationAnswers exactly and that null forgets the answer. The description restates those semantics rather than adding new ones, so the baseline 3 is appropriate.

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 pair (change or forget) on a specific resource (the answer auto-apply reuses for one employer question), and scopes it to a single question. The mention of readApplicationAnswers makes clear this tool writes while that sibling reads, so an agent can separate the two without opening either 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 concrete operating guidance: take the question verbatim from readApplicationAnswers, only change what the candidate asked for, in their own words, and use null to forget. It also notes a later real answer supersedes the edit. It stops short of an explicit when-not or a named alternative for adjacent needs, so a 4 rather than a 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