Skip to main content
Glama

Read Auto apply

get_auto_apply
Read-onlyIdempotent

The member's Auto apply settings and résumés, how wide the settings let Auto apply and how many jobs each setting leaves out. Actions: settings, reach. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "get_auto_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "settings",
      -  "help"
      -]New value: +[
      +  "settings",
      +  "reach",
      +  "help"
      +]
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered and the description needn't repeat it. It does add substantive behavioral context about what reach measures (how wide settings allow Auto apply and how many jobs each setting excludes), but says nothing about pagination, limits, or what happens with an unset Auto apply profile.

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?

Two short sentences plus a help pointer, with the action list front-loaded. The first sentence is a noun-phrase fragment rather than a clause, which slightly reduces readability but wastes no words.

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?

For a read-only tool with no output schema and a free-form nested params object, the description gives enough to pick an action and a discovery path via help. It leaves the shape of the returned settings and reach data unspecified, which an agent would have to learn by calling.

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 50%: action has an enum but no per-value description, and params is an open-ended object. The description compensates by glossing settings and reach and by explicitly deferring field discovery to action "help", which is a workable substitute for documenting the nested params object.

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 a specific resource (the member's Auto apply settings and résumés) and enumerates the two read actions, settings and reach, with a gloss on what each returns. It is clearly a read tool and distinct from the write-oriented sibling update_auto_apply, though it never names the sibling explicitly.

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?

It tells the agent which actions exist and routes it to action "help" for per-action fields, which is genuine procedural guidance. It does not say when to choose reach over settings, nor when to use this instead of update_auto_apply, so selection context is only implied.

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.