Skip to main content
Glama

TrueInterview

Report setup progress

report_setup_progress
Idempotent

Tell the candidate how the setup they handed you is going: they watch these stages on TrueInterview while you work. Give the run_code from the setup instructions, the stage and its status: active when you start a stage, waiting with needs when the candidate has to do something (say exactly what, in one line), completed or skipped when it is done, failed with a one-line note when it cannot go on. The stages, in order: connect_agent, check_profile, complete_profile, confirm_search, find_jobs, prepare_application, fill_in_browser, await_submit, logged. TrueInterview completes logged itself when report_application says the first application went in. The candidate fills and submits the form themselves: fill_in_browser is them filling it, await_submit is them pressing Submit. A note or needs is one short line for the candidate and never holds a password, a code, an ID number or a form answer.

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": {
      "run_code": "<run_code>",
      "stage": "<stage>",
      "status": "<status>"
    },
    "name": "report_setup_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
needsNoWith status waiting: what the candidate has to do.
stageYes
statusYes
run_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only say this is a non-destructive idempotent write; the description adds real behavioral context: the candidate sees these updates live, the ordering of the nine stages, that `logged` is system-completed via `report_application`, and a privacy rule forbidding passwords, codes, IDs, and form answers in notes. It does not describe what a call returns or what happens on an out-of-order stage report, which the absent output schema leaves unexplained.

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-loads the purpose, then enumerates stages, then exceptions and privacy constraints — a sensible order. Some sentences are long and run-on (the status enumeration), but no sentence is redundant given the low schema coverage.

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 five-parameter reporting tool with no output schema, the description covers stage enumeration and order, status semantics, cross-tool interaction with `report_application`, and content restrictions. An agent has everything needed to emit a correct call.

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 only 20%, so the description must carry meaning, and it does: `run_code` comes from the setup instructions, `stage` values are given in required order, `status` values are given semantics, and `needs` is bound to `waiting` with a 'say exactly what, in one line' rule. `note` is only implicitly defined (one short line, used with `failed`), leaving its role for other statuses slightly ambiguous.

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 audience: report to the candidate how setup is going, with the candidate watching named stages on TrueInterview. It also distinguishes its own stage `logged` from what `report_application` triggers, so an agent can separate the two reporting tools without opening a 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 explicit per-status guidance: `active` on stage start, `waiting` with `needs` when the candidate must act, `completed`/`skipped` when done, `failed` with a one-line note when blocked. It also clarifies that `fill_in_browser` and `await_submit` are candidate actions, not agent actions. It lacks an explicit negative case (e.g., when not to report), which keeps it from 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