Skip to main content
Glama

AceRound AI Interview Copilot

preview_job_application_form

Read-only

Pre-apply check: show the application form for a job from the job library, what is prefilled from the user's profile and resume, and which required items are missing. Does not apply or charge; open questions are answered by AI at apply time. (Requires the user's sign-in with scope job_applications:read.)

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": {
      "campusJobId": "<campusJobId>"
    },
    "name": "preview_job_application_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
campusJobIdYesJob id, from search_campus_jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the description's job is to add context beyond that — and it does, disclosing the required auth scope (job_applications:read), the absence of any application submission or charge, and the fact that unresolved questions are handled later at apply time. It does not discuss caching, rate limits, or whether the preview must be re-run after profile edits, which keeps it short of a 5.

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 capability is front-loaded in a single dense sentence, with the safety/scope caveat and auth requirement appended in a compact parenthetical. It is slightly run-on in places, but every clause carries information an agent needs.

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?

With one parameter, no output schema, and annotations covering the safety profile, the description supplies what remains: what the preview contains, that nothing is submitted or billed, and that authentication with a specific scope is required. Return shape details (field ordering, whether partial prefill is listed per-field) are unspecified but not essential for correct invocation.

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 coverage is 100% and the single parameter is documented as a job id sourced from search_campus_jobs. The description reinforces that the job comes 'from the job library' but adds no id format or validation detail beyond the schema, so the baseline 3 applies.

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?

The description names a specific verb and resource ('show the application form for a job from the job library') and enumerates the three things it returns: the form, the profile/resume prefill, and missing required items. It explicitly separates itself from the apply/submit siblings with 'Does not apply or charge', so an agent can tell it apart from the many mutation tools in the sibling list.

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?

'Pre-apply check' states the moment to use it, and 'Does not apply or charge; open questions are answered by AI at apply time' rules out using it as the actual apply step. There is no explicit named alternative for the real submission path, but the negations give clear context for when this tool is and is not appropriate.

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