Skip to main content
Glama
jobhunt

jobhunt

by athulanish

check_job_risk

Scans job postings for scam signals like fees, chat-app interviews, free-email recruiters, lookalike domains, and ID/bank requests, then verifies the role on the company's Greenhouse or Lever board.

Instructions

Look for scam signals in a job posting: fees, chat-app interviews, free-email recruiters, lookalike domains, requests for ID or bank details. Also checks whether the role exists on the company's own Greenhouse or Lever board. Returns signals, not a verdict.

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": {
      "company": "<company>"
    },
    "name": "check_job_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
titleNo
companyYes
descriptionNo
verify_boardNo
contact_emailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does disclose two important traits: it makes an external lookup against the company's Greenhouse/Lever board, and it deliberately returns signals rather than a pass/fail judgment. It does not say what the output looks like, whether the board check can fail or slow the call, or what happens when the company name is ambiguous — meaningful gaps for a zero-annotation tool.

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

Conciseness5/5

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

Two sentences, both dense with unique information: the first enumerates the signals checked, the second adds the board-verification behavior and the output caveat. Nothing repeats the name or wastes words, and the primary purpose is front-loaded.

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

Completeness3/5

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

With no annotations, no output schema, and six undocumented parameters, the description should do more work than it does. It covers purpose and one behavioral caveat well, but leaves the agent without any sense of return shape or per-parameter usage, which is a real gap for a tool this parameterized.

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

Parameters2/5

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

Schema coverage is 0% across six parameters, so the description must compensate and largely does not. It hints at the board-verification toggle and at contact_email (via 'free-email recruiters'), but never clarifies that 'description' is the raw posting text, what 'url' or 'title' are used for, or that only 'company' is required — leaving an agent to guess at half the inputs.

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?

The description names a specific verb+resource ('look for scam signals in a job posting') and then enumerates the concrete signals checked: fees, chat-app interviews, free-email recruiters, lookalike domains, ID/bank-detail requests. It also states a second, distinct behavior (verifying the role against Greenhouse/Lever boards), which no sibling tool covers, so an agent can separate this from check_cv_health or compare_cv_to_job without opening a 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?

The scope is unambiguous — this tool is for assessing a posting's legitimacy — and the closing line 'Returns signals, not a verdict' sets expectations about how to use the output. There are no explicit exclusions or named alternatives, but the domain is narrow enough that the when-to-use condition is clear from the description alone.

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