Skip to main content
Glama

RemoteHunt

Can this job hire me?

can_job_hire_me
Read-onlyIdempotent

Check whether one RemoteHunt job can hire a person who lives in a given country, from where the posting says it hires. Takes a RemoteHunt job link (remotehunt.app/job/...).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job": "<job>",
      "country": "<country>"
    },
    "name": "can_job_hire_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesA RemoteHunt job link or its slug.
countryYesCountry the person lives in: a name or an ISO code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, non-destructive and closed-world, so the safety profile is covered. The description usefully discloses that the verdict is derived from 'where the posting says it hires', warning that the answer is only as reliable as the posting data, but it says nothing about the return shape (a boolean, a country list, a reason) and no output schema exists to fill that gap.

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?

Two short sentences with the core purpose front-loaded and zero filler. The second sentence is a minor restatement of what the schema already says about the job parameter, keeping it just below top marks.

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

Completeness4/5

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

For a two-parameter read-only lookup with full schema coverage and complete annotations, the description covers the computation basis and the required input format. The only real gap is the undisclosed result shape, which is notable because no output schema exists.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented in structured data, setting the baseline at 3. The description adds a partial URL format hint ('remotehunt.app/job/...') but actually narrows the schema's stated 'link or its slug' to link-only, contributing little new meaning.

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

Purpose4/5

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

The description pairs a specific verb ('check whether') with a precise resource ('one RemoteHunt job can hire a person in a given country'), which is an eligibility verdict rather than a fetch or search, so it is intrinsically distinct from get_job and search_remote_jobs. It does not name or explicitly contrast those siblings, so it falls short of the top tier.

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

Usage Guidelines3/5

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

Usage is implied by the input constraint ('Takes a RemoteHunt job link'), which tells the agent this is a per-job eligibility check. There is no guidance on when not to use it or what to call instead when the job is not on RemoteHunt, leaving the agent to infer.

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.

Resources