freelance-radar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADZUNA_APP_ID | No | Your Adzuna application ID (optional; enables the Adzuna source when set together with ADZUNA_APP_KEY) | |
| SSL_CERT_FILE | No | Path to a custom CA bundle to trust behind a TLS-intercepting proxy (optional) | |
| ADZUNA_APP_KEY | No | Your Adzuna application key (optional; enables the Adzuna source when set together with ADZUNA_APP_ID) | |
| REQUESTS_CA_BUNDLE | No | Path to a custom CA bundle to trust behind a TLS-intercepting proxy (optional) |
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 |
|---|---|
| source_statusA | Report which job sources are live and why — call this first to see what you're actually querying before trusting the results. |
| search_jobsA | Search every configured job source and return normalized postings. Args: query: free-text search, e.g. "automation" or "shopify developer". category: optional Remotive category slug, e.g. "software-dev". limit: max postings per source (1-50). |
| score_opportunitiesA | Search job sources, then score every result against your own capability keywords (0-100, title matches weighted 2x body matches). Highest score first. Args: capability_keywords: e.g. ["MCP", "python", "automation", "shopify", "API integration"]. query: free-text search passed through to the sources. category: optional Remotive category slug. limit: max postings per source before scoring. |
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 3 tools
source_status is clearly a distinct diagnostic, and score_opportunities is differentiated from search_jobs by its explicit scoring/ranking behavior. The overlap between search_jobs and score_opportunities (both query sources and return postings) is real, but descriptions make the boundary legible.
All names use snake_case and are readable, following a verb_noun style for the two action tools (search_jobs, score_opportunities). The noun-first source_status is a minor deviation but clearly conveys its purpose.
Three tools is on the lean side but well matched to a focused job-radar purpose: check sources, search, and score. Nothing feels redundant or padded for the stated scope.
The core loop (verify sources, search, score) is covered, but there is no way to fetch full details for a single posting, filter by region/rate, or persist/track scored opportunities. These are noticeable gaps for a job-hunting workflow, though an agent can work around them.