Skip to main content
Glama

Read my saved application answers

readApplicationAnswers
Read-onlyIdempotent

What auto-apply puts on employer forms without asking the candidate. remembered lists earlier answers it reuses when a form asks the same question. defaults lists what goes on every form, from their profile or a fixed default (assumed true); value null means that question waits for the candidate. missingBasics names the facts most forms ask that the profile still lacks (address, phone, start date, salary expectation): offer to add them with editPreferences so fewer forms stop to ask. selfIdentification lists the voluntary gender, race, veteran, disability and pronoun answers (declined until the candidate picks one); set one with editApplicationAnswer using its question, only when the candidate says so. Fix a default's value with editPreferences; change or forget a remembered answer with editApplicationAnswer.

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the bar is lower; the description still adds real semantics such as 'assumed true' for defaults, 'value null means that question waits for the candidate', and 'declined until the candidate picks one'. It also discloses that inputs and results are privately recorded for usage tracking, a behavioral trait absent from the annotations. It stops short of describing result size or ordering, which the output schema presumably covers.

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?

Nearly every clause carries information, and the remediation paths are paired with their target tools rather than listed separately. The text is one dense paragraph with an awkward first sentence, which makes it harder to scan than a short bulleted structure would be, but there is no filler.

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?

An output schema exists, so return values need not be explained, yet the description goes further and interprets each field's meaning and the action each implies. For a zero-parameter read tool this covers everything an agent needs before calling it and before acting on the result.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning for the description to add or omit. Nothing in the text misleads about inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description concretely enumerates what the tool exposes (remembered, defaults, missingBasics, selfIdentification) so an agent knows this is the saved-answer store used by auto-apply. It is specific about the resource, though the opening sentence describes the concept ('what auto-apply puts on employer forms') rather than stating a verb like 'returns', so the action is inferred from the name.

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 routes the agent explicitly: offer editPreferences for missingBasics, fix a default with editPreferences, change or forget a remembered answer with editApplicationAnswer. It also imposes a hard condition on the risky path ('set one with editApplicationAnswer ... only when the candidate says so'), which is exactly the when/when-not guidance an agent needs.

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