Skip to main content
Glama

Mark a person yes or no

setRoleSearchDecision

Mark one person a Search found (person id from getRoleSearch) as a yes or no for the role, with up to 5 short reasons. On a normal Search it only records the call: nobody is contacted, introduced, shortlisted or passed, and the next run learns from it. On the Sourcing feed of a role (people Clera's sourcing run approved and has not contacted yet), a yes contacts a real person: Clera finds their email and starts outreach for the role, or puts them on the LinkedIn queue when no email is found. Make a yes there only when the user explicitly asks to reach out to that person, and say first that it starts outreach; a no contacts nobody and frees the person for Clera's other roles. A call is final: once anyone on the team has marked a person, it can't be changed, and only Searches with a role take calls. Use the user's own call and reasons, never decide for them, and read the call back to them before making it.

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": {
      "roleSearchId": "<roleSearchId>",
      "roleSearchPersonId": "<roleSearchPersonId>",
      "decision": "<decision>"
    },
    "name": "setRoleSearchDecision"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
reasonsNo
decisionYes
roleSearchIdYes
roleSearchPersonIdYes

Output Schema

NameRequiredDescriptionDefault
runYes
decisionYes
outreachNoteYes
feedbackLedgerIdYes
roleSearchPersonIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it explains that a normal Search call is recorded only and feeds the next run, while a Sourcing-feed yes finds an email and starts outreach or queues for LinkedIn, and a no frees the person for other roles. It also discloses irreversibility (once anyone on the team marks a person it can't be changed) and a data-recording notice, which the annotations do not convey.

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 core action, then conditional branches, then constraints and safety rules. It is denser than ideal in places (the Sourcing-feed sentence runs long), but nearly every sentence carries information an agent needs to avoid an irreversible mistake.

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 five-parameter, non-idempotent, externally visible action, the description covers mode-dependent effects, prerequisites, irreversibility, and user-consent requirements. An output schema exists, so the absence of return-value detail is not a gap.

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 only 20%, and the description compensates for the key fields: roleSearchPersonId is sourced from getRoleSearch, reasons are capped at 5 short entries, and decision's yes/no meaning is explained per context. orgId is not discussed, though the schema documents it inline, so the gap is minor.

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?

Opens with a specific verb and resource: mark one person a Search found as yes or no for the role, with up to 5 reasons. It ties the person id back to getRoleSearch and separates the two contexts (normal Search vs Sourcing feed), so an agent can distinguish it from siblings like getRoleSearch or undoMatchDecision.

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 when-to-use and when-not rules: on a Sourcing feed a yes starts real outreach and should only be made when the user explicitly asks and after stating the consequence; on a normal Search it only records. It also states the precondition that only Searches with a role accept calls, and that the agent must use the user's own call and read it back first.

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