Skip to main content
Glama

Ask a candidate something

askCandidate

Ask a candidate who is interviewing for one of your roles a question, through Clera: availability, a detail of their background, what they think of the role. Clera's agent for the candidate answers what it already knows and asks the candidate for the rest.

Take opportunityId from a listPipeline row of a candidate in an interview process. request is what the user wants to know, in the user's words, self-contained and naming the role; it reaches the candidate's agent and can be put to the candidate. Confirm the wording with the user before calling. The answer arrives later: listAsks shows each ask's status and, once answered, its outcome.

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

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
requestYesWhat the user wants to know, in their words, self-contained and naming the role.
opportunityIdYesThe opportunityId of the candidate's listPipeline row.

Output Schema

NameRequiredDescriptionDefault
askIdYes
messageYes
expiresAtYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover safety (readOnly=false, destructive=false, idempotent=false) but nothing about the async or outward-facing nature of the call. The description discloses the key behaviors: the request reaches a third-party agent and may be put to the candidate verbatim, the answer arrives asynchronously later via listAsks, and inputs are privately logged for tracking and support. That is meaningful context the annotations do not provide.

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 short paragraphs, front-loaded with purpose, then mechanics, then the async return path and the disclosure. Usage details and caveats are ordered usefully. The final privacy sentence is boilerplate but short enough to be tolerable; nothing is redundant with the annotations or schema.

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 non-destructive, non-idempotent, open-world write with an output schema, the description supplies exactly the missing pieces: where the ID originates, how careful wording must be, that the result is deferred and where to retrieve it. Since an output schema exists, return-value detail is correctly omitted.

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 schema describes all three parameters; the description must therefore add meaning, and it does by specifying where opportunityId comes from (a listPipeline row of a candidate in an interview process) and by emphasizing that request is the user's own self-contained wording naming the role and is delivered to the candidate's agent. It adds provenance and audience context rather than merely restating 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 and resource (ask a candidate a question), names the channel it travels through (Clera's candidate agent), and enumerates the kinds of questions it supports. It also distinguishes itself from listAsks (which reports outcomes) and listPipeline (which supplies the opportunityId), so an agent can place it among siblings without opening other schemas.

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 concrete when-to-use examples (availability, background detail, opinion of the role) plus procedural guidance: pull opportunityId from a candidate's listPipeline row in an interview process, and confirm wording with the user before calling. It also routes the agent elsewhere for the answer via listAsks. It stops short of an explicit when-not-to-use statement, keeping it at a 4 rather than a 5.

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