Civil Exam Position Filter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CPF_CONFIG | No | Path to the YAML configuration file. Overridden by the --config command-line argument. | |
| CPF_DATA_DIR | No | Data directory path. Precedence: --data-dir > CPF_DATA_DIR > config data_dir > ./data |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| import_positionsC | Import a local user-supplied table. Writes SQLite; identical imports are skipped. |
| filter_positionsD | Screen parsed conditions conservatively; unknown clauses require manual review. |
| explain_positionC | Explain source rules and outcomes; ambiguous codes require a table ID. |
| search_majorsC | Search the local replaceable catalogue subset; no network request. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool maps to a distinct stage of the workflow: import (load data), search_majors (catalogue lookup), filter_positions (screening), and explain_position (rule/outcome explanation). The boundary between filter_positions and explain_position is the only mild overlap, since both deal with parsed conditions, but the descriptions distinguish screening from explaining.
All four tools follow the same verb_noun snake_case pattern: explain_position, import_positions, filter_positions, search_majors. Minor singular/plural variation (position vs positions) exists but the convention is clearly consistent.
Four tools is a tight, well-scoped set for a position-filtering server: one per core operation (import, search, filter, explain). Nothing appears redundant or missing in terms of count.
The core lifecycle is covered: import source data, search the catalogue, filter positions, and explain outcomes. Minor gaps exist around managing imported tables (no list/delete/refresh operation) and no export of filtered results, but agents can work around these.