Skip to main content
Glama

Enter an application verification code

enterApplicationCode
Destructive

Finish an applyToJob run that is waiting on something the employer emailed the candidate; getApplicationRun then reports verificationCodeRequested. Greenhouse and similar sites email a short code after the first submit click; Workday sites (apply URLs on myworkdayjobs.com) email a link to verify the candidate account the run just created. When the run used the Clera apply address, readApplyInbox shows the code; otherwise ask the candidate for the code, or the full link from the 'Verify your candidate account' email, and pass it here exactly as they give it. The run enters the code or opens the link and continues; check getApplicationRun again for the outcome. Never guess a code.

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

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": {
      "runId": "<runId>",
      "code": "<code>"
    },
    "name": "enterApplicationCode"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code, or the full verification link, from the employer's email, exactly as the candidate gave it.
runIdYesThe runId applyToJob returned.

Output Schema

NameRequiredDescriptionDefault
acceptedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations it explains the effect of the call: the run enters the code or opens the link and continues, and the agent should re-check getApplicationRun for the outcome. It also discloses that inputs and results are privately recorded for usage tracking and support, and that the run may create a candidate account on Workday. It does not explain why the tool is flagged destructive or non-idempotent, which is the remaining gap given the annotations already declare those hints.

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-loaded with the purpose and run state, then branching guidance, then the follow-up step, with no filler sentences. The paragraph is dense and long, but nearly every clause carries actionable information; the privacy-recording sentence is boilerplate but short.

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?

Covers what the tool does, when to invoke it, where the input comes from in each environment, what happens after, and how to verify the outcome. With an output schema present and annotations carrying the safety profile, nothing critical for correct invocation is missing.

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 the baseline is 3, but the description adds real meaning: the code parameter may be either the short emailed code or the full 'Verify your candidate account' link, and it must be passed exactly as given. It does not add detail on runId beyond the schema, which is reasonable.

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 resource (enter a verification code) and names the exact run state it resolves (applyToJob run waiting on an employer email, verificationCodeRequested). It also distinguishes the two site families (Greenhouse short code vs Workday myworkdayjobs.com link), so an agent can tell this apart from siblings like readApplyInbox or getApplicationRun.

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?

Gives explicit preconditions (run reports verificationCodeRequested), explicit sourcing rules (readApplyInbox when the Clera apply address was used, otherwise ask the candidate), and an explicit prohibition (never guess a code). It also points to the follow-up check via getApplicationRun, leaving little to inference.

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