Skip to main content
Glama

Worklittle Jobs

Jobs · Get Apply Settings

get_apply_settings
Read-onlyIdempotent

Jobs — Get the user's apply settings: auto_apply (Worklittle applies to matching jobs on its own), auto_submit (submit without a review stop), tailor_resume (tailor the resume to each job) and max_per_company (most applications to one company in any 30 days; say it with the 30 days).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real context beyond that by explaining what each setting actually does in behavior terms (auto_apply applies on the user's behalf, auto_submit skips the review stop) and by specifying the 30-day window semantics for max_per_company. It omits anything about auth or account state, but the annotations lower the bar here.

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?

A single sentence that front-loads the resource and then defines each field inline. It is dense but every clause carries information; the nested parentheses make it slightly harder to scan than it needs to be, and "say it with the 30 days" is idiosyncratically worded.

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?

A zero-parameter read-only getter with an output schema and full annotation coverage needs little more. The description supplies the interpretation of each returned setting, which is the main thing an agent could otherwise get wrong when relaying values to a user.

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 the baseline is 4 and there is no parameter meaning the description could add or omit. The parenthetical glosses apply to returned fields rather than inputs, which is a bonus rather than a requirement.

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?

States a specific verb and resource ("Get the user's apply settings") and enumerates exactly which settings are returned. The read-vs-write distinction from the sibling update_apply_settings is inferable from the name and verb, but the description never names that sibling explicitly, so it stops short of a 5.

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 no explicit when-to-use statement, no mention of checking settings before calling update_apply_settings, and no prerequisites or exclusions. Usage is only implied by the fact that it returns current values an agent would read prior to a mutation.

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