Skip to main content
Glama

TrueInterview

What an application needs

get_application_checklist
Read-onlyIdempotent

What an application form will ask for, before helping with one: which facts the candidate's résumé already has on file (name, email, phone, location, a profile link, work history, education), which are missing and how to add them (fix_in_chat first, fix_url for the website), the questions still to ask the candidate because neither the résumé nor their saved answers settle them (work authorization, salary, start date), and what only their computer has. For the résumé it says whether a fact is on file, not the fact: get_resume has the document. A connection that may also update the profile gets saved_answers too, the answers the candidate saved with update_application_answers, and setup: whether the answers every form needs are there (where they may work), each gap with the question to ask word for word and its options, the postal-address answers still open (address_missing, asked only when a form asks for the address), and prefill, what the résumé already says, to put to the candidate as a yes. Ask those only when the candidate starts applying (prepare_application lists them then), not when they connect or search, and save them with update_application_answers. Nothing is stored and nothing goes to an employer.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and openWorldHint false, so the safety profile is covered. The description adds useful behavior beyond that: nothing is stored, nothing goes to an employer, résumé facts are reported only as present/absent, and saved_answers/setup appear only for connections that may update the profile.

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

Conciseness2/5

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

The content is relevant because there is no output schema, but it is delivered in three very long, nested sentences full of semicolons and parentheticals. The dense run-on structure makes the tool hard to scan and could be reorganized into a short list without losing 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 zero-parameter read tool with no output schema, the definition explains the conditional output shape thoroughly: base checklist, saved_answers, setup, prefill and the timing for asking setup questions. An agent has enough information to call it correctly, though the prose density reduces usability.

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 has zero parameters, so there are no parameter semantics for the description to explain. The baseline score for zero-parameter tools is 4.

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 opening clause names the resource clearly: what an application form will ask for, in the context of helping with one. It explicitly distinguishes its résumé presence flags from get_resume's actual document. The verb is implied by the name rather than stated up front, so it is very clear but not perfectly action-front-loaded.

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 says exactly when to ask the setup questions: only when the candidate starts applying, with prepare_application named as the timing trigger, and explicitly not when they connect or search. It also routes saving answers to update_application_answers, giving both timing and alternative-tool guidance.

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