Skip to main content
Glama

find_past_answers

Read-onlyIdempotent

Retrieve answers from previous job applications to reuse them when filling new forms, including notice period, salary, or reason for leaving. Search by question words to read full responses.

Instructions

Form answers the person gave on earlier applications (kept by save_application_package), newest application first: key, company, title, applied, question and answer; without a query each question once, with asked (how many applications had it) and only the first line or so of its answer: search for the question's words to read it whole. Use it before filling a form, to reuse what was answered to "reason for leaving", "notice period" or "salary" instead of writing it again; for everything sent with one application use get_application_package.

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

Input Schema

NameRequiredDescriptionDefault
limitNoAt most this many, newest first; hundreds of distinct questions pile up across applications, so search with a query rather than raising it.
queryNoWords of the question to look for ("notice period", "reason leaving"): every word must be in the question, any case. Empty lists each distinct question once, with the start of its latest answer.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 50,
      +  "description": "At most this many, newest first; hundreds of distinct questions pile up across applications, so search with a query rather than raising it.",
      +  "minimum": 1,
      +  "title": "Limit",
      +  "type": "integer"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Words of the question to look for (\"notice period\", \"reason leaving\"): every word must be in the question, any case. Empty lists each distinct question once, with its latest answer."New value: +"Words of the question to look for (\"notice period\", \"reason leaving\"): every word must be in the question, any case. Empty lists each distinct question once, with the start of its latest answer."
  2. Addedv0.6.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial context beyond them: the data's origin (kept by save_application_package), newest-application-first ordering, and the crucial difference in results with and without a query — deduplicated questions with an "asked" count and truncated first lines versus full answers.

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?

It is front-loaded with what the tool returns and dense with no filler sentences; every clause carries information. The semicolon-chained, run-on construction makes it heavier reading than it needs to be, but nothing is redundant.

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 two-parameter read tool with an output schema and full annotations, the description covers origin, ordering, both calling modes, and the alternative tool. An agent can invoke it correctly and interpret its results without any further information.

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 100%, so baseline is 3; the description still adds value by explaining why not to raise the limit (hundreds of distinct questions accumulate) and by defining query matching as all-words-must-appear in the question, any case. It also ties truncation to the fix — search a word to read the answer whole.

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 names the resource precisely — form answers from earlier applications — and enumerates the returned fields (key, company, title, applied, question, answer), plus names the sibling get_application_package for the whole-package case. The opening clause is a fragment ("Form answers the person gave...") rather than a verb+resource statement, which makes it slightly slower to parse, but the intent is unmistakable.

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 states exactly when to call it ("Use it before filling a form") with concrete examples ("reason for leaving", "notice period", "salary") and explicitly routes the other use case to get_application_package. It also distinguishes the two calling modes: no query for a one-per-question overview versus a query to read an answer whole.

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