Skip to main content
Glama

Undo a pass

undoPass
Destructive

Undo a prior pass on a candidate, putting them back in your review list. Use this when the company asks to undo or reverse a pass for a candidate from listPassed.

Pass opportunityId, talentName and roleName copied verbatim from the same listPassed entry; all three must describe one entry. A mismatch between the names and the opportunity is refused, so never substitute a different role for the same talent. Only a passed candidate can be restored; if the opportunity is not a company pass, say so and restore nothing.

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": {
      "opportunityId": "<opportunityId>",
      "talentName": "<talentName>",
      "roleName": "<roleName>"
    },
    "name": "undoPass"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
roleNameYesThe role name, copied verbatim from the same list row. Checked against the opportunity; a mismatch is refused, so never substitute a different role for the same talent.
talentNameYesThe talent's name, copied verbatim from the list row you are acting on. Checked against the opportunity; a mismatch is refused.
opportunityIdYesThe opportunity ID from listPassed.

Output Schema

NameRequiredDescriptionDefault
roleNameYes
talentNameYes

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?

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, but the description adds substantial context beyond them: cross-field validation that refuses name/opportunity mismatches, the precondition that the candidate must actually be passed, the instruction to report rather than proceed on failure, and a disclosure that inputs and results are logged. These are the operational facts an agent needs before invoking a mutation tool.

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?

Three tight, front-loaded sentences that move from purpose to input rules to failure behavior, with no repetition of the schema. The final privacy/logging sentence is somewhat boilerplate but is short and discloses something an agent would not otherwise know.

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 mutation with four parameters and an output schema, the description covers purpose, precondition, input provenance, validation failure handling, and user-facing response instruction. With return values handled by the output schema, nothing material is missing for correct invocation.

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 earns extra credit by adding a group-level constraint the schema only states per-field: opportunityId, talentName and roleName must all be copied verbatim from one listPassed entry and must describe the same entry. It does not mention orgId, but the schema documents that adequately.

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 ('Undo a prior pass on a candidate') plus the concrete effect ('putting them back in your review list'). It also names the sibling listPassed as the origin of the entry, so an agent can distinguish this from passCandidate or undoMatchDecision without opening any schema.

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?

Explicitly states the trigger condition ('when the company asks to undo or reverse a pass'), the source of valid inputs (listPassed), and the negative case ('if the opportunity is not a company pass, say so and restore nothing'). This is close to a complete when-to-use and when-not-to-use rule.

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