Skip to main content
Glama

Pass on a match

declineMatch
DestructiveIdempotent

Pass on a role, the same as the pass button on a Matches card. The role leaves the Matches list and Clera stops working on it; undoMatchDecision brings it back.

Pass position and companyName exactly as the row gave them; a mismatch is refused.

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": {
      "jobId": "<jobId>",
      "position": "<position>",
      "companyName": "<companyName>",
      "reason": "<reason>"
    },
    "name": "declineMatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe jobId from a listMatches or listMyPipeline row.
reasonYesWhy this role doesn't fit, in the candidate's own words or a fact on file: salary, location, seniority, domain, whichever they raised.
positionYesThe position exactly as the row gave it.
reasonCodeNoThe reason the candidate gave, picked from the same list the Matches card offers: salary_expectations (the comp is too low for them), location_mismatch (the location or remote setup doesn't work for them), visa (they need a sponsorship or work permit the role can't give), company_mismatch (they don't want this company), role_mismatch (not the kind of role they do), seniority_mismatch (too junior or too senior for them), candidate_not_searching (not looking right now), other (anything else, in their words). Pass it whenever the candidate said why.
companyNameYesThe company name exactly as the row gave it.

Output Schema

NameRequiredDescriptionDefault
jobIdYes
statusYes
positionYes
companyNameYes
referralUrlYes
opportunityIdYes
applyOwnershipYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint, idempotentHint), the description discloses the concrete consequence — the role leaves the Matches list and Clera stops working on it — plus the recovery route via undoMatchDecision. It also warns that mismatched position/companyName is refused, and notes that inputs and results are recorded for usage tracking and support, which is exactly the kind of authorization/privacy context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short paragraphs, front-loaded with the effect, then the exact-copy constraint, then the disclosure note. No sentence restates the name or title, and nothing is padding.

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?

With full schema coverage, an output schema, and rich annotations, the description only needed to add effect, reversibility, and the verbatim-input rule — and it does all three. An agent has everything required to invoke this correctly and understand what changes afterward.

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 already 100%, so the baseline is 3, but the description adds real meaning: position and companyName must be passed verbatim as the row gave them or the call is rejected. That failure-mode constraint is not visible in the schema and changes how the agent must source those values.

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?

"Pass on a role, the same as the pass button on a Matches card" gives a specific verb plus resource and anchors it to a UI action the agent can reason about. It also names the reversal sibling (undoMatchDecision), so the operation is distinguishable from a generic pass/decline without opening a schema.

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?

The description establishes context (acting on a Matches card row) and states the reversal path via undoMatchDecision, which tells the agent this decision is recoverable rather than final. It does not explicitly exclude other candidates such as passCandidate or passJob, but the Matches-card framing implicitly scopes it to roles surfaced in the matches list.

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