Skip to main content
Glama

Look up filter values

suggestFilterValues
Read-onlyIdempotent

Resolve real, indexed values for searchCandidates filters before using them. work_history and education_history only match EXACT company/school names; always resolve the user's phrasing ('Figma', 'TUM', 'Stanford') to indexed values with this tool first, then pass those values to searchCandidates as plain filters or boolean_tags.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "field": "<field>",
      "query": "<query>"
    },
    "name": "suggestFilterValues"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYesWhich filter's vocabulary to search: work_history = employer company names, education_history = school names, location = current-location strings, languages = spoken languages, plus role_names, skills, job_types and preferred_work.
limitNo
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
queryYesPartial text to match. Word-prefix matching with synonyms for common acronyms; 'Munich' or 'TUM' finds 'Technical University of Munich'. Try another word from the name when a lookup misses.

Output Schema

NameRequiredDescriptionDefault
successYes
suggestionsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is settled. The description adds genuinely new behavior: work_history and education_history only match EXACT company/school names, which is a hard constraint that would otherwise cause silent empty results. It also discloses that inputs and results are recorded for usage tracking, a privacy trait no annotation conveys.

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 key constraint and the workflow are front-loaded in the first sentence, and the second sentence explains why the tool exists. The trailing privacy note is somewhat boilerplate but is a legitimate disclosure rather than filler; nothing else could be cut without losing meaning.

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 present, the description does not need to explain return values, and it covers the workflow, the exact-match trap, and the miss-handling path. The only gap is that it never relates this tool to listFilterOptions, so an agent must infer which one enumerates a filter vocabulary.

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?

Schema coverage is 75%, so the baseline is 3; the description earns an extra point by making the field/query interaction concrete, spelling out that work_history and education_history require exact indexed names while query is the user's loose phrasing ('Figma', 'TUM', 'Stanford'). It says nothing about limit or orgId, which the schema largely carries on its own.

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 gives a specific verb+resource: resolve real, indexed values for searchCandidates filters. It clearly positions itself as a lookup step that feeds searchCandidates, so an agent can tell it is not the search tool itself. It does not distinguish itself from the sibling listFilterOptions, which is the one remaining ambiguity.

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 states an explicit mandatory ordering ('always resolve ... with this tool first, then pass those values to searchCandidates') and names the downstream consumer of the results. It also handles the failure case by telling the agent to retry with another word from the name when a lookup misses.

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