Skip to main content
Glama

Undo a like or pass

undoMatchDecision
DestructiveIdempotent

Reset a like or a pass so the role is back in Matches as new, the same as undo on the dashboard. Take the opportunityId from listMyPipeline (a declined row) or listMatches.

Only the candidate's own decision is reset: a role Clera or the company closed (no_match, not_submitted, closed) stays that way, and a role already in process cannot be pulled back here; withdrawFromProcess does that.

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>"
    },
    "name": "undoMatchDecision"
  }
}

Input Schema

NameRequiredDescriptionDefault
opportunityIdYesThe opportunityId from listMyPipeline or listMatches.

Output Schema

NameRequiredDescriptionDefault
positionYes
companyNameYes
opportunityIdYes
previousDecisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description adds genuinely non-structured behavior: only the candidate's own decision is reset, closed states are preserved, and inputs/results are privately recorded for usage tracking and support — a disclosure the agent could not get from annotations or schema.

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?

The behavior statement is front-loaded and the follow-up sentences each carry a distinct constraint (state preservation, the alternative tool, the data-recording notice). Slight redundancy with the schema's parameter description keeps it from being tight enough for a 5.

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 an output schema present and full schema coverage, the description only needs to supply behavior and routing, and it largely does: mutation scope, persistence of closed states, ID provenance, and the withdrawFromProcess alternative. The unresolved overlap with undoPass is the only meaningful omission for a one-parameter mutation tool.

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% and the single opportunityId parameter is fully documented there. The description's provenance hint ('take the opportunityId from listMyPipeline (a declined row) or listMatches') nearly duplicates the schema text, so it adds little beyond it — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (reset a like or pass so the role returns to Matches as new) and anchors it with a concrete analogy (same as undo on the dashboard). It clearly separates itself from withdrawFromProcess, but it never distinguishes itself from the sibling named undoPass, which sounds like it covers the same ground, leaving one routing ambiguity.

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 context by naming where the opportunityId comes from (a declined row in listMyPipeline, or listMatches). It also states the negative cases directly: a role the company closed (no_match, not_submitted, closed) stays closed, and a role already in process needs withdrawFromProcess instead.

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