Skip to main content
Glama

Book an interview

bookInterview
Destructive

Book the candidate's next interview round with the hiring manager at a time from listInterviewSlots. The hiring manager and the candidate both get a calendar invite, so the candidate gets one confirmation first. Only book a time the candidate picked. outcome booked: done. pending: the scheduler confirms within minutes, so don't call it booked yet. handoff: send the candidate handoffUrl to finish it themselves.

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>",
      "start": "<start>",
      "timeZone": "<timeZone>"
    },
    "name": "bookInterview"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYesOne start exactly as listInterviewSlots listed it.
answersNoThe candidate's answers to the booking form's open questions, keyed by each question's slug.
timeZoneYesThe timezone exactly as listInterviewSlots named it.
eventTypeSlugNoThe meeting type's slug, as listInterviewSlots listed it.
opportunityIdYesThe opportunityId of a process row from listMyPipeline.
confirmBookingNoOnly when your client cannot show the confirmation prompt: "confirm" once the candidate has said yes to this role and time, "cancel" otherwise. Never set it on your own.

Output Schema

NameRequiredDescriptionDefault
roleYes
labelYes
startYes
outcomeYes
handoffUrlYes
meetingUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the annotations: it explains that both the hiring manager and candidate receive calendar invites, that the candidate gets one confirmation first, and it decodes the three outcome states (booked = done, pending = scheduler still confirming within minutes so do not report as booked, handoff = send the candidate handoffUrl). That outcome decoding is the kind of behavioral detail annotations cannot carry and directly changes how the agent reports results.

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?

Purpose and the candidate-confirmation rule are front-loaded, and the terse outcome lines are scannable and dense with decision-relevant information. The fragmentary phrasing ('outcome booked: done.') is slightly brittle, and the trailing data-recording sentence is boilerplate, but neither wastes much space.

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?

For a 6-parameter mutating tool with a nested answers object and an existing output schema, the definition covers the essentials: prerequisites, candidate consent, dual calendar invites, and how to interpret each terminal outcome. It does not address failure modes (slot taken, expired handoff, invalid timeZone) or the confirmBooking escape hatch, which is left entirely to the schema.

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 every parameter, including answers and the confirm/cancel enum, is documented in the schema itself. The description only reinforces the provenance constraint on start/timeZone by tying them to listInterviewSlots output, which is useful but does not add per-parameter meaning beyond the schema.

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 (book), a specific resource (the candidate's next interview round with the hiring manager), and the source of valid inputs (a time from listInterviewSlots). An agent can distinguish this from acceptInterview, setInterview, or 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?

Gives an explicit prerequisite (the time must come from listInterviewSlots) and a hard constraint (only book a time the candidate picked), which is exactly the guard an agent needs before invoking a write. It stops short of naming when a sibling such as rescheduleInterview or acceptInterview is the better choice, so it is clear context rather than a full routing 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