Intermediair Jobs
Server Details
Search and retrieve job postings on Intermediair (read-only).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 2 of 2 tools scored.
The two tools have clearly distinct roles: search_jobs for querying the catalogue and get_job for retrieving full details by ID. There is no ambiguity or overlap.
Both tool names follow a consistent verb_noun pattern in snake_case: search_jobs and get_job, making the set predictable and easy to understand.
With only 2 tools, the server feels minimal. While it covers the basic search-and-detail workflow, the low count is borderline thin for a job search domain.
The surface covers the core use case of searching and viewing job details. Minor gaps like listing categories or filtering options are handled within the search tool, so overall it is reasonably complete.
Available Tools
2 toolsget_jobGet jobARead-onlyIdempotentInspect
Fetch the full details of a single job posting by id. Use this after search_jobs to retrieve the complete description, requirements, salary breakdown, and company information for a listing. Returns an error result if the id is unknown.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric or UUID job identifier. Get this from search_jobs results. |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | |
| url | Yes | |
| title | Yes | |
| salary | Yes | |
| company | Yes | |
| location | Yes | |
| categories | Yes | |
| industries | Yes | |
| careerLevel | Yes | |
| description | Yes | |
| contractType | Yes | |
| customFields | Yes | |
| requirements | Yes | |
| workingHours | Yes | |
| workingPlace | Yes | |
| educationLevel | Yes | |
| publishingDate | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. Description adds that the tool returns full details and an error for unknown ids, which is useful but not extensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences: first states purpose, second gives usage context and error case. No wasted words, front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool is low complexity (1 param, output schema exists). Description covers purpose, usage, and error behavior completely. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema already covers the id parameter with pattern and description. Description reinforces that id comes from search_jobs but adds minimal semantic value beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Fetch the full details of a single job posting by id' with specific verb 'Fetch' and resource 'job posting'. Distinguishes from sibling tool search_jobs by targeting a single item.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises to use after search_jobs and describes error behavior for unknown id, providing clear when-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_jobsSearch jobsARead-onlyIdempotentInspect
Search the live Dutch job catalogue for openings matching the given criteria. Use this when the user wants to find jobs by role, location, salary, contract type, remote/onsite preference, or education level. Each result carries an id you can pass to get_job for the full record. Pagination metadata (page, totalPages, total) is included so the client can decide whether to fetch the next page.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page index. Combine with 'limit' for pagination. | |
| sort | No | Sort order. 'relevance' weighs the query, 'date' is freshness, 'distance' requires 'location', 'popularity' weighs view count. | relevance |
| limit | No | Number of results to return. Capped at 25 to keep responses compact; use pagination for more. | |
| query | No | Free-text keywords. Optional; if omitted, returns the most recent jobs matching the other filters. | |
| category | No | Filter by job category (the on-site 'Vakgebied' filter). Multi-select. Dutch values, e.g. 'Automatisering/Internet' (IT), 'Medisch/Zorg' (medical/care), 'Marketing/PR/Communicatie'. | |
| distance | No | Search radius in kilometres around the given location. Use 'city' for an exact city match or '0' for nationwide (500 km). | |
| industry | No | Filter by industry (the on-site 'Branche' filter). Multi-select. Dutch values, e.g. 'ICT', 'Gezondheidszorg/Welzijn', 'Onderwijs/Opleiding'. | |
| location | No | Dutch city, municipality, or province name. Combined with 'distance' for radius search. | |
| postedBy | No | Filter by who posted the listing. 'direct_employer_and_media_bureau' = direct employer, 'human_resource_manager' = third-party recruiter. Omit to include both. | |
| salaryMin | No | Minimum gross monthly salary in euros. Discrete steps: 0, 1500, 2500, 3500, 5000, 7000. | |
| careerLevel | No | Filter by career level. Multi-select. Dutch values: 'Geen ervaring' (no experience), 'Starter', 'Ervaren' (experienced), 'Leidinggevend' (manager), 'Senior management', 'Directie' (board). | |
| contractType | No | Filter by contract type. Multi-select. Dutch labour-market values: 'Vast' (permanent), 'Tijdelijk' (temporary), 'Freelance', 'ZZP' (self-employed), 'Stage' (internship), etc. | |
| workingPlace | No | Filter by work arrangement. 'remote' = work from home only, 'hybrid' = mixed, 'onsite' = office only. | |
| educationLevel | No | Filter by required education level. Multi-select. Use the Dutch abbreviation: 'WO' (university), 'HBO' (applied university), 'MBO' (vocational), etc. | |
| employmentType | No | Filter by hours. 'fulltime' = 33-40h/week, 'parttime' = 1-32h/week. Omit to include both. |
Output Schema
| Name | Required | Description |
|---|---|---|
| jobs | Yes | |
| page | Yes | 1-based index of the page returned (echo of the input `page`). |
| total | Yes | Total number of matching jobs across all pages. |
| totalPages | Yes | Total number of pages available for this query at the current `limit`. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint as safe. The description adds behavioral details: pagination metadata included, results contain IDs for get_job, and it searches 'live' data. There is no contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three focused sentences: purpose, usage, and output format. No redundant information; every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (15 parameters, output schema exists), the description covers the core functionality, linking to sibling, and pagination behavior. It is sufficient for an agent to understand when and how to invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so parameters are already documented in the schema. The description summarizes the filter categories but does not add new semantic information beyond the schema for parameters. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches the 'live Dutch job catalogue' with specific criteria. It distinguishes from the sibling 'get_job' by noting that results contain IDs for further detail. The verb 'search' and the resource are explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Use this when the user wants to find jobs by...' which is direct guidance. However, it does not explicitly state when not to use it or provide alternatives besides get_job for details, but the sibling relationship is implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!