Skip to main content
Glama

Read my Autopilot

readAutopilot
Read-onlyIdempotent

The candidate's Autopilot: the saved job board searches (at most 3) Clera re-runs three times a day, which are on, whether each application waits for their OK (reviewBeforeSubmit), whether it writes tailored documents, whether the review queue holds it back (status) and when the next pass runs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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.5/5.0
Behavior4/5

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

Annotations already establish readOnly=true, idempotent=true, destructive=false, so safety framing is covered. The description adds real context beyond that: the three-per-day re-run cadence, the cap of 3 saved searches, the meaning of status as review-queue gating, and the fact that inputs/results are privately logged for usage tracking — a disclosure not present in annotations.

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?

Front-loading is good — the resource is named in the first words. However, the first sentence is a single long run-on chain of subordinate clauses that is harder to scan than a short bulleted enumeration would be, and the privacy/usage-tracking sentence, while relevant, sits slightly apart from the core description.

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?

For a zero-parameter read with an output schema, this is close to complete: state, cadence, caps, and gating semantics are all surfaced. The mild redundancy of enumerating the returned fields when an output schema exists is harmless rather than harmful.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No misleading parameter language is present.

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 resource precisely and enumerates exactly what it reports: saved searches (max 3), cadence (three times a day), on/off state, reviewBeforeSubmit, tailored-document writing, review-queue status, and next pass time. That is far more specific than the name alone. It doesn't explicitly contrast with the sibling editAutopilot/editAutopilotSearch tools, so sibling differentiation is only implied by the read framing.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives such as editAutopilot or listMyPipeline, and no prerequisites or exclusions. An agent can infer it is the 'inspect current configuration' call, but the inference comes from the field list, not from any explicit guidance.

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