Skip to main content
Glama

Check an applicant for fraud

checkApplicant
Read-onlyIdempotent

Check an applicant from the company's own hiring process against every fake profile Clera has already caught. Pass any of email, phone or linkedinUrl; more identifiers catch more repeat fakes.

matched is true when one of the identifiers belongs to a profile Clera confirmed fake or flagged. Each match says which identifiers matched (matchedOn), whether it is a confirmed fake or only flagged, when it was first flagged, and the reasons in plain words. The matched profiles themselves are never returned.

matched false means Clera has no fake-profile record for these identifiers. It is not proof the applicant is real, so say that plainly. Triggers: "is this applicant legit", "check jordan@… for fraud", "have you seen this phone number before", a pasted CV header with contact details.

Clera privately records this tool's inputs and results for usage tracking and support.

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": "checkApplicant"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe applicant's email address.
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
phoneNoThe applicant's phone number with at least 10 digits, any format.
linkedinUrlNoThe applicant's LinkedIn profile URL (linkedin.com/in/…).

Output Schema

NameRequiredDescriptionDefault
matchedYes
matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag a safe, idempotent read, and the description adds substantial context beyond them: the matched/matchedOn structure, confirmed-fake vs flagged distinction, first-flagged date, plain-language reasons, that matched profiles are never returned, and the privacy/usage-tracking notice. It also warns that a false result is not proof of legitimacy.

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?

Purpose is front-loaded, then result semantics, then triggers, then the privacy note — a sensible order with little redundancy. It is on the long side, but nearly every sentence carries decision-relevant information.

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?

Although an output schema exists, the description still explains the meaning of a true and false result and the important caveat about false negatives, plus the recording notice. For a 4-parameter check tool with no required fields, nothing an agent needs to call it correctly is missing.

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 the baseline is 3; the description adds real meaning by framing the identifiers as optional and additive ('more identifiers catch more repeat fakes'), which the schema does not convey. The orgId parameter is left to its schema description, so it stops short of a 5.

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 and resource ('Check an applicant ... against every fake profile Clera has already caught') and scopes it to the company's own hiring process. This clearly separates it from siblings like checkResumeForAts or checkContactLookup without needing their schemas.

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 concrete invocation triggers ('is this applicant legit', 'have you seen this phone number before', pasted CV header) and clarifies the identifier strategy: any of email/phone/linkedinUrl, with more identifiers catching more repeat fakes. It lacks explicit 'when not to use' or named alternatives (e.g. setFraudVerdict), keeping it from 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.

Resources