Skip to main content
Glama

Turn my apply address on or off

setApplyInbox
Idempotent

Choose whether auto-apply puts the candidate's Clera apply address on applications instead of their own email. With it on, employer mail lands in readApplyInbox, verification codes reach the waiting application run without the candidate pasting them, and Clera forwards each email to their own address. Turning it on the first time creates the address. Confirm with the candidate before switching.

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": {
      "useForApplications": "<useForApplications>"
    },
    "name": "setApplyInbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
useForApplicationsYestrue puts the Clera apply address on applications; false uses their own email.

Output Schema

NameRequiredDescriptionDefault
forwardsToYes
aliasAddressYes
useForApplicationsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive toggle, so the description focuses on consequences: first enablement creates the address, mail routes into readApplyInbox, verification codes flow to the waiting application run, and emails are forwarded. It also discloses that inputs and results are recorded for usage tracking and support. It omits what happens to previously routed mail if switched off.

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 effect of the toggle, then behaviors, then the confirmation instruction. The closing data-recording sentence is boilerplate but short; no sentence is badly out of place.

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?

With one fully documented parameter, an output schema present, and annotations covering the safety profile, the description covers everything an agent needs to decide and invoke correctly, including downstream effects on readApplyInbox and pending application runs.

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% and the single boolean is self-documenting, so the baseline is 3; the description adds real meaning by explaining both sides of the flag (on routes mail to Clera, off uses the candidate's own email) rather than just restating true/false.

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: toggling whether auto-apply uses the Clera apply address instead of the candidate's own email. It also names the related readApplyInbox tool, making the boundary between configuring the address and reading its mail explicit.

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 a clear operational context (auto-apply behavior) and an explicit procedural requirement: "Confirm with the candidate before switching." It does not spell out when to prefer leaving it off, but the when-to-use condition is clear enough to act on.

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