Skip to main content
Glama

4dayweek.io Jobs

Search companies

search_companies
Read-onlyIdempotent

Search employers by their working-hours policy.

This answers "which companies offer a 4-day week" style questions at the employer level, where the policy actually lives, rather than per listing. The same schedule_type semantics as search_jobs apply: "compressed_week" is a 4x10 and is not a 4-day week.

Two location facts are separate and are often confused. country is where the employer is based. hires_worldwide is whether it accepts applicants from any country. remote_level is its office-presence policy, and a fully-remote employer can still hire in one country only.

Each result carries the employer's name, slug, url, schedule type, full-time hours, remote level and count of open roles. get_company takes the slug and returns the full profile.

Paging works as in search_jobs: at most 25 employers per call, with page, page_size, returned, total_matching, has_more and next_page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number. Default 1, maximum 200.
sortNoResult order. One of score (work-life score, highest first), jobs (most open roles), alphabetical, newest. Omit for the site's default order.
limitNoResults per page. Default 10, maximum 25.
queryNoFree-text search over company name and website.
countryNoCountry name. This is where the employer is based, which is a different question from where it will hire — see hires_worldwide.
has_jobsNoOnly employers with at least one live listing.
remote_levelNoThe employer's office-presence policy. One of fully-remote, hybrid, onsite. Independent of hires_worldwide: a fully-remote employer can still hire in one country only.
schedule_typeNoFilter by the employer's schedule policy, e.g. 4_day_week.
hires_worldwideNoOnly employers that accept applicants from any country.

Output Schema

NameRequiredDescriptionDefault
noteNo
pageNo
has_moreNo
returnedNo
companiesNo
next_pageNo
page_sizeNo
paging_noteNo
total_matchingNo
paging_limit_reachedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower, and the description still adds real behavioral context: paging semantics (25 max, page/page_size/returned/total_matching/has_more/next_page), the field set returned, and two semantic traps (compressed_week is a 4x10, not a 4-day week; country vs hires_worldwide vs remote_level are separate facts). No auth or rate-limit details, but none are needed for a public read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose before any caveats, and each paragraph carries a distinct payload (routing, semantics, location disambiguation, return shape, paging). Slightly long, and the 'each result carries...' sentence partly duplicates the existing output schema, so it falls short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter search tool with an output schema and full annotation coverage, the description is complete: it covers routing to siblings, the semantic pitfalls, and full paging contract. Nothing an agent needs to call it correctly is missing, and return values are appropriately left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description clears that bar by adding meaning the schema lacks: the schedule_type semantics ('compressed_week' is 4x10 and not a 4-day week) and page-size defaults. It repeats the country/hires_worldwide/remote_level distinctions verbatim from the schema, which is redundant rather than additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+scope: 'Search employers by their working-hours policy,' and immediately frames the level of abstraction ('at the employer level, where the policy actually lives, rather than per listing'). It explicitly contrasts with the sibling search_jobs and names get_company for the follow-up, so an agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear routing context: use this for employer-level policy questions, use search_jobs for per-listing questions, and use get_company (via slug) for the full profile. It lacks an explicit 'do not use when...' exclusion, but the alternative-tool mapping is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.