Skip to main content
Glama

Mark a candidate fake

setFraudVerdict
DestructiveIdempotent

Mark a candidate Clera showed this company as fake, or clear that mark, the same as the Fraud detection page on the dashboard. Use it when someone on the company says a candidate is fake, a fraud, not a real person or using someone else's identity, and asks to flag them; when it is only a suspicion, ask before marking.

marked_fake applies to the candidate across all of Clera, not just this company: their open intros close, they come off every list, and Clera stops contacting them. cleared undoes that and reopens their file.

Only for a candidate this company was shown; anyone else is refused. Only owners and editors can do it. For an applicant from the company's own hiring process, use checkApplicant instead.

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

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": {
      "talentId": "<talentId>",
      "decision": "<decision>"
    },
    "name": "setFraudVerdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
decisionYesmarked_fake when the company says the candidate is fake; cleared when they say a candidate marked fake is real after all.
talentIdYesThe candidate's talentId from listPipeline, readShortlist, listRecommendedCandidates or listPendingIntroRequests. A candidate found only through searchCandidates was never shown to the company and is refused.

Output Schema

NameRequiredDescriptionDefault
messageYes
outcomeYes

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 declare destructiveHint=true and idempotentHint=true, and the description goes well past them: it explains that the mark is global across all of Clera, closes open intros, removes the candidate from every list, and stops all contact — and that 'cleared' reverses this and reopens the file. It also discloses the permission requirement and the private input/result logging, which no structured field carries.

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 action and the when-to-use rule, then consequences, then eligibility. It is on the long side and repeats the 'candidate this company was shown' constraint that the schema also carries, plus a privacy notice, but every paragraph still carries information an agent needs.

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 destructive, cross-tenant mutation this covers what changes, how to reverse it, who may call it, what is refused, and which sibling to use instead; an output schema exists so return values need not be described. Nothing required to invoke it correctly is missing.

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 all three parameters (orgId, decision, talentId) are already documented with enum values and sourcing tools. The description only reinforces the talentId restriction (candidate must have been shown to the company, else refused), which the schema already states, so it adds little beyond the baseline.

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 ('mark a candidate ... as fake, or clear that mark') and immediately scopes it to candidates 'Clera showed this company', which separates it from checkApplicant and from search-only candidates. The dashboard analogy plus the talentId phrasing make the target object unambiguous.

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

Usage Guidelines5/5

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

Gives explicit triggering conditions ('someone on the company says a candidate is fake ... and asks to flag them'), a caution for the borderline case ('when it is only a suspicion, ask before marking'), and a named alternative ('For an applicant from the company's own hiring process, use checkApplicant instead'). Eligibility constraints (candidate must have been shown to this company; owners/editors only) are stated too.

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