Skip to main content
Glama

Accept an interview invitation

acceptInterview
Idempotent

Accept a pending interview invitation from listInterviewRequests. Clera tells the company and follows up with scheduling; the candidate does not need to email anyone. Confirm the role and stage with the candidate first; this is the answer the company gets.

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": "acceptInterview"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.2/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, idempotent, open-world write, but the description adds context they cannot: Clera notifies the company and handles scheduling follow-up, and the candidate need not email anyone. It also discloses private logging of inputs and results, which is genuinely new behavioral information beyond the annotations.

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 core is front-loaded in two efficient sentences covering action, side effect, and prerequisite. The closing privacy/logging sentence is boilerplate that dilutes focus but does carry disclosure value.

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 one-parameter mutation with an output schema, the description covers everything needed: where the ID originates, the external consequence of accepting, the prerequisite check, and the data-handling note. Nothing required for correct invocation is missing.

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 coverage is 100% and the single parameter's description already explains it is a pending row from listInterviewRequests, so the description largely restates that. The 'confirm the role and stage' line is a workflow caution rather than added meaning about the parameter value itself.

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 opens with a specific verb and resource ('Accept a pending interview invitation') and names the sibling that produces the required ID (listInterviewRequests). An agent can distinguish this from declineInterview or rescheduleInterview without inspecting 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 states the precondition clearly: the ID comes from listInterviewRequests, and the agent should confirm role and stage with the candidate before acting. It does not explicitly contrast with declineInterview or rescheduleInterview, so it stops short of full when/when-not routing.

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