Skip to main content
Glama

Read the user's settings

freeapply_get_settings
Read-onlyIdempotent

Read the user's profile, targets, eligibility, résumé, and automation settings so an agent can score jobs or fill forms using only accurate, user-provided facts.

Instructions

Reads the user's settings: who they are, what they seek and how FreeApply should work. Single form answers: freeapply_manage_answers; whether FreeApply can run: freeapply_get_status. Use: once per session or helper, and again after each auto-run go, before scoring jobs or filling a form. With the résumé text and the user's own words, the only source of facts about the user: never invent beyond it. To change: freeapply_update_settings. Behavior: read-only; never includes installation secrets. Parameters: sections, the sections to return (default all, named under Returns): ask only for what the step needs, e.g. ["profile", "eligibility"] for a form, and leave out resume, the largest, unless you need its text. Returns: {settings, missing}. Sections: profile, targets, eligibility, resume (file paths, text, profile; the user adds and replaces résumé files in the dashboard), cover_letter, automation, autorun, gmail, custom_answers, models, model_choices, sharing (choices only). missing: required fields still empty [{key, label}]; while non-empty, apply nowhere: open the settings tab (freeapply_open_dashboard) and ask the user to fill them. Errors: an unknown section; the message lists valid ones.

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

Input Schema

NameRequiredDescriptionDefault
sectionsNoSection names to return (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.6
    • changedInput schema / properties / sections / description
      Previous value: -"Sections to return (default all), e.g. [\"profile\", \"eligibility\"] for a form; omit resume, the largest, unless you need its text."New value: +"Section names to return (default all)."
  2. Changed1 schema field changedv1.0.4
    • changedInput schema / properties / sections / description
      Previous value: -"Sections to return. Optional; default all."New value: +"Sections to return (default all), e.g. [\"profile\", \"eligibility\"] for a form; omit resume, the largest, unless you need its text."
  3. Changed1 schema field changedv1.0.2
    • addedInput schema / properties / sections
      Added value: +{
      +  "description": "Sections to return. Optional; default all.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  4. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations' read-only/idempotent hints, it discloses security context ('never includes installation secrets'), an epistemic constraint ('the only source of facts about the user: never invent beyond it'), and critical gating behavior: while `missing` is non-empty, 'apply nowhere' and the agent should open the settings tab. It also describes error behavior for unknown sections.

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?

The description is front-loaded and broken into labeled segments (Use, Behavior, Parameters, Returns, Errors), with no wasted sections. It is dense but mostly earns its length; the sentence 'With the résumé text and the user's own words, the only source of facts about the user: never invent beyond it' is slightly awkward and could be clearer.

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?

For a one-parameter read tool with rich annotations but no output schema, the description covers everything an agent needs: return shape ({settings, missing}), the full section list, missing-field gating, and error handling. Nothing material is missing to call or interpret it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents the `sections` parameter at 100% coverage, so the baseline is 3. The description significantly adds meaning by enumerating valid section names under Returns, advising to request only what the step needs with a concrete example, and warning that `resume` is the largest and should be omitted unless its text is required.

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?

The description opens with a specific verb and resource: 'Reads the user's settings: who they are, what they seek and how FreeApply should work.' It explicitly distinguishes itself from freeapply_manage_answers, freeapply_get_status, and freeapply_update_settings, so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

It gives explicit timing: 'once per session or helper, and again after each auto-run go, before scoring jobs or filling a form.' It also names the alternatives for single-form answers and status checks, and directs changes to freeapply_update_settings. When and when-not are both covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.