Skip to main content
Glama

Decline an interview invitation

declineInterview
DestructiveIdempotent

Decline a pending interview invitation from listInterviewRequests. The company is told; give the reason the candidate wants passed on, kept short and plain. Confirm with the candidate first, this cannot be undone here.

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": {
      "interviewProgressId": "<interviewProgressId>"
    },
    "name": "declineInterview"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy, in the candidate's words, if they want it passed on.
interviewProgressIdYesThe interviewProgressId of a pending row from listInterviewRequests.

Output Schema

NameRequiredDescriptionDefault
stageYes
positionYes
responseYes
companyNameYes
interviewProgressIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already disclose destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false. The description adds genuinely non-structured facts: the company is notified, the action 'cannot be undone here', and a human confirmation step is expected — solid added context. It loses points for not saying what happens if the invitation is no longer pending, and the tracking/privacy sentence is generic boilerplate rather than behavior an agent can act on.

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 functional sentences, front-loaded with the action and its precondition, and the confirmation warning comes before the call is made. The trailing 'Clera privately records...' disclosure is boilerplate that does not help tool selection, costing a little efficiency.

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 full schema coverage, an output schema, and rich annotations, the description covers the essentials: target source, side effect on the company, irreversibility, and the confirm-first workflow. The only residual gap is failure/staleness behavior, which is acceptable given the structured data available.

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, but the description adds actionable meaning: the reason is passed on to the company and should be 'kept short and plain' (a tone/length constraint the 1000-char schema does not convey). It also reinforces that interviewProgressId must be a pending row from listInterviewRequests.

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?

The description states a specific verb+resource ('Decline a pending interview invitation') and names the exact source of valid targets ('from listInterviewRequests'), which routes the agent to the right sibling. It is clearly distinguishable from acceptInterview/rescheduleInterview 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 Guidelines4/5

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

It sets a clear precondition (invitation must be 'pending' and come from listInterviewRequests) and a workflow requirement: 'Confirm with the candidate first.' It does not explicitly name the alternative action (accepting) or state what to do if the row is no longer pending, so it stops short of full when/when-not coverage.

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