poslovi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| 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 |
|---|---|
| search_jobsA | Search job postings on Serbian job boards. Args: query: Search terms, e.g. "python developer" or "AI engineer". board: "infostud", "helloworld", or "all" (default) for both. page: Results page, starting at 1. Returns: JSON list of postings with title, company, url, board, and id. |
| get_jobA | Fetch one job posting and return its full details. Args: url: Posting URL returned by search_jobs. Returns: JSON object with title, company, location, dates, employment type, qualifications, and the posting text. |
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 2 tools
The two tools have clearly distinct purposes: search_jobs lists job postings matching a query, while get_job retrieves full details for a specific posting. No overlap or ambiguity exists.
Both tools follow a consistent verb_noun pattern (search_jobs, get_job), making the naming predictable and easy to understand.
With only 2 tools, the set is minimal but appropriate for a focused read-only job board API. It slightly undershoots the typical 3-15 range but still feels well-scoped.
The tools cover the core read operations (search and detail retrieval) for job postings. Missing features like filtering by location or job type are minor gaps that don't severely impact usability.