Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ONET_MATCH_BUNDLENoPath to a bundle directory to serve your own model instead of downloading from the Hugging Face Hub
ONET_MATCH_HF_REPONoHugging Face repo (owner/repo) to load the model bundle from

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
match_occupationsA

Match free text about work to the closest O*NET occupations.

    text: a job title, resume bullet, job posting, project description, interest statement or
    skill list. top_k: number of occupations to return (1-20). Returns ranked occupations with
    SOC codes, calibrated confidence, key tasks and skills, plus an aggregate skill and RIASEC
    interest profile.
    
get_occupationA

Full O*NET record for one occupation by SOC code (e.g. "15-1252.00"): description, tasks, detailed work activities, skills, knowledge, abilities and RIASEC interests.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct roles: match_occupations performs free-text matching and ranking, while get_occupation retrieves a full record by SOC code. There is no realistic overlap or misselection risk because one is discovery and the other is lookup.

Naming Consistency5/5

Both names follow the same verb_noun snake_case pattern: match_occupations and get_occupation. The convention is predictable and readable.

Tool Count4/5

Two tools is slightly thin relative to the typical 3-15 range, but the server has a narrow purpose and each tool earns its place. Adding more tools would likely be unnecessary unless the server expands beyond matching and record retrieval.

Completeness4/5

The surface covers the core workflow: find occupations from free text, then retrieve the full O*NET record for a chosen SOC code. Minor gaps exist, such as no explicit listing or bulk retrieval of SOC codes, but agents can work around this through matching.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues