Skip to main content
Glama

Change my Autopilot settings

editAutopilot
DestructiveIdempotent

Whether each Autopilot application waits for the candidate's OK (reviewBeforeSubmit) and whether it writes a tailored resume and cover letter (tailorDocuments). reviewBeforeSubmit false means real applications go to employers with nobody checking them first, so it asks the candidate to confirm, every time. Only when the candidate asked for it.

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

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

Input Schema

NameRequiredDescriptionDefault
tailorDocumentsNo
reviewBeforeSubmitNo
confirmSendWithoutReviewNoOnly when your client cannot show the confirmation prompt: "send_without_review" once the candidate has said yes to Autopilot sending applications without their OK, "cancel" otherwise. Never set it on your own.

Output Schema

NameRequiredDescriptionDefault
statusYes
searchesYes
nextRunAtYes
tailorDocumentsYes
reviewBeforeSubmitYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description earns credit by explaining what makes it destructive: turning off reviewBeforeSubmit sends real applications to employers with nobody checking them. It also discloses that Clera records inputs and results. It does not explain the consequences of the confirmSendWithoutReview escape hatch beyond what the schema already says.

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

Conciseness3/5

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

The opening clause is dense but front-loads the two settings correctly; however, the fragment 'so it asks the candidate to confirm, every time. Only when the candidate asked for it' is ambiguous about who asks and what 'it' refers to. The privacy-tracking sentence is boilerplate but short.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the destructive effect is well covered. Still missing for a three-parameter, zero-required mutation tool is whether omitted fields are left unchanged and whether the candidate confirmation must precede or follow the call, both of which an agent needs to invoke it safely.

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 33%, so the description has to carry weight, and it does: it defines the meaning and real-world effect of both undocumented booleans (reviewBeforeSubmit, tailorDocuments) rather than restating their names. The third parameter is left to its own schema description, which is acceptable since that description is unusually detailed.

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 description names the two specific settings this tool changes (reviewBeforeSubmit and tailorDocuments) and explains what each controls, which is enough for an agent to recognize a settings-mutation tool and separate it from editAutopilotSearch or readAutopilot. It never states the verb directly ('use this to change settings'), so the purpose is inferred from the title plus the field semantics rather than asserted.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is real guidance for the confirmation flow: setting reviewBeforeSubmit to false is described as consequential and the caller is told to ask the candidate to confirm every time, and only when the candidate requested it. What is missing is any statement about when to call this at all versus reading current settings first, or how partial updates behave given that no parameters are required.

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