Skip to main content
Glama

Kariaa Agents

Check a job post or offer for scam signs

check_job_post
Read-only

Use when the person asks whether a job post, recruiter message or offer is legit or a scam. Returns warning signs (fees, upfront payments, personal email domains, link shorteners, pressure, requests for ID or bank details), each with the exact quoted line. Rule-based. Pass the text in English; translate it first if needed, keeping amounts, links, phone numbers and emails exactly as written.

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": {
      "text": "<text>"
    },
    "name": "check_job_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe full post or message, in English

Output Schema

NameRequiredDescriptionDefault
riskNolow, elevated or high
signalsNoWarning signs, each with the quoted evidence
translate_firstNoTrue when the post must be translated to English first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly and non-destructive, but the description adds genuinely new behavior: the check is 'rule-based' (deterministic, not model judgment) and returns each warning sign with 'the exact quoted line,' which tells the agent how to present results. It does not discuss limits of the rule set or what an empty result means, leaving a small 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?

Four sentences, front-loaded with the trigger and the return shape, then the implementation note, then the input constraint. Every sentence carries information, though the translation/preservation instruction could be tightened slightly.

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?

With one required parameter, full schema coverage, annotations, and an output schema, the definition covers the trigger, the return content and the language precondition, which is enough to call it correctly. Only minor edge details (behavior on very short or non-English-without-translation input) are unstated, and those are handled by the schema bounds.

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% and already says the text must be in English, but the description adds operational meaning the schema lacks: translate first if needed, and preserve amounts, links, phone numbers and emails exactly as written so the detector can match them. That is real guidance beyond the field definition.

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 states a specific check ('whether a job post, recruiter message or offer is legit or a scam') and enumerates the exact signal classes returned, so the agent knows this is scam-pattern detection rather than job retrieval like get_job or search_jobs. Purpose is unambiguous from the first sentence.

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?

It gives an explicit trigger condition — 'when the person asks whether a job post, recruiter message or offer is legit or a scam' — which is concrete and actionable. It does not state when not to use it or name an alternative tool, so it falls short of a 5.

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.