Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
resolve_companyA

Turn company names into the Lever site names that address their job boards, and report every instance that answered. search_jobs resolves names on its own, so reach for this to check which of several companies are on Lever at all: it probes names without reading a single board, where a search would read one per company.

search_jobsA

Search the openings published by named companies on Lever. companies takes company names or Lever site names, and each name is turned into a site name here. A name found on the first spelling costs 3 requests, and one that resists costs up to 9, at one second each. location, team, department and commitment are sent to Lever and need its exact wording. keyword, workplace_type, country, salary and recency are applied here, because Lever accepts none of them as filters. limit applies per company, so a company whose openings fill it may publish more. posted_within_days walks up to 5 pages per company, because Lever pages by title and a recent opening sits anywhere.

get_jobA

Read one Lever opening in full: the advert, its named sections, and the salary as published. company_slug and instance are the ones the row carried, and a site living on both instances holds different openings on each.

list_filter_valuesA

List the team, location and commitment wordings one company uses on Lever, so a filter can carry the words that company publishes. The vocabulary belongs to each company: one writes Full-time, another Full Time, another EE Full-Time. Lever publishes no vocabulary for department, so a department filter is checked against the openings a company has open right now.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 4 tools

Disambiguation4/5

search_jobs and resolve_company share the company-name-resolution step, but the descriptions clearly separate probing which companies are on Lever from actually reading job boards. get_job and list_filter_values have distinct purposes. There is still a small moment of hesitation over whether to call resolve_company first, but otherwise the tools are easy to tell apart.

Naming Consistency5/5

All four tools use a consistent snake_case verb_noun pattern: search_jobs, resolve_company, get_job, list_filter_values. The convention is predictable and readable throughout.

Tool Count5/5

Four tools is a well-scoped set for a read-only Lever job-search server. Each tool earns its place: search, company resolution, job detail, and filter vocabulary lookup.

Completeness4/5

The read-only lifecycle is covered: resolving company names, searching openings, reading a full job, and listing filter vocabularies. Minor gaps remain, such as no direct department-vocabulary listing and no way to browse all Lever companies without naming them, but agents can work around these.

Maintenance

ActivityActive
ResponsivenessUnresponsive