Skip to main content
Glama

Read my preferences

readPreferences
Read-onlyIdempotent

The candidate's job preferences and profile data as the Preferences page holds them: salary range, whether it is base or on-target earnings (salary_basis, plus any separate OTE range) and how much it matters, work environment, preferred cities, relocation, roles, job types, industries, company size and funding stage, visa needs, availability, how actively they are looking (appetite), whether Clera may intro them without asking first (allow_direct_submission), blocked companies, skills, name, phone, LinkedIn, GitHub, portfolio and X links, whether auto-apply tailors documents, and the postal address and work-authorized countries (ISO-2) job applications are filled with.

Matching runs on these, so an unset or stale field is the first thing to fix when matches look off. Keys match editPreferences one to one. memory lists the notes Clera keeps about the candidate (motivations, constraints, contact habits); editPreferences memory changes them.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
phoneYes
rolesYes
x_urlYes
memoryYes
skillsYes
appetiteYes
lastnameYes
timezoneYes
firstnameYes
job_typesYes
github_urlYes
other_linksYes
linkedin_urlYes
salary_basisYes
notice_periodYes
portfolio_urlYes
postal_addressYes
ote_lower_boundYes
ote_upper_boundYes
salary_currencyYes
years_experienceYes
blocked_companiesYes
salary_importanceYes
cover_letter_notesYes
preferred_industryYes
salary_lower_boundYes
salary_upper_boundYes
location_importanceYes
available_start_dateYes
job_types_importanceYes
preferred_job_commentYes
visa_sponsorship_typeYes
allow_company_outreachYes
preferred_company_sizeYes
allow_direct_submissionYes
visa_sponsorship_neededYes
willingness_to_relocateYes
work_authorized_countriesYes
autopilot_tailor_documentsYes
preferred_work_environmentYes
preferred_work_geolocationsYes
visa_sponsorship_importanceYes
preferred_company_funding_stageYes
visa_sponsorship_further_detailsYes
preferred_work_environment_importanceYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, non-destructive read, so the description's job is to add context beyond that — and it does: matching depends on these values, memory notes are Clera's private annotations about the candidate, and there is a privacy disclosure that inputs and results are recorded for usage tracking and support. It does not discuss caching or freshness of the returned data, which is the main remaining gap.

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

Conciseness2/5

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

The opening sentence is a roughly ninety-word field inventory, and the highest-value guidance (matching depends on these values) is buried at the start of the second paragraph. Since an output schema exists, that long enumeration of returned fields is largely redundant with structured data rather than earning its place. The privacy sentence is boilerplate at the tail.

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?

With an output schema and full annotations supplied, the description covers the pieces that matter: what the data is used for, how stale values affect matching, and how the related memory field is edited. It is complete enough to call correctly and interpret the result, with only data-freshness behavior left implicit.

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 no parameters, so there is no argument semantics to explain and the baseline of 4 applies. The description does not need to compensate for schema gaps.

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 identifies a specific resource (the candidate's job preferences and profile data as the Preferences page holds them) and enumerates its scope in detail, so an agent knows exactly what comes back. It also anchors the shape to editPreferences ("Keys match editPreferences one to one"). It lacks an explicit verb phrase like "Returns all preferences," so it reads as a data description rather than a stated action.

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

Usage Guidelines4/5

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

It gives a concrete triggering condition: "Matching runs on these, so an unset or stale field is the first thing to fix when matches look off." It also implies the modification path by noting editPreferences changes memory notes. A fully explicit "use editPreferences to modify these fields" is absent, but the routing is clear enough to act on.

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