Skip to main content
Glama

Answer a role question

answerRoleQuestion
DestructiveIdempotent

Save the candidate's answer to one of a company's role questions, from listMatches or readMatch. The questions are the company's own screening questions; Clera passes the submitted answers on with the introduction.

Draft first and read the answer back before submitting: submit true marks it final and it goes to the company, which cannot be taken back, so get the candidate's yes first. Answer in the candidate's own words and facts, never invented ones. Refuses a questionId that is not on one of the candidate's matches.

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": {
      "questionId": "<questionId>",
      "answer": "<answer>"
    },
    "name": "answerRoleQuestion"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerYesThe answer, in the candidate's own words.
submitNofalse saves a draft the candidate can still change; true submits it.
questionIdYesThe questionId from listMatches or readMatch.

Output Schema

NameRequiredDescriptionDefault
statusYes
questionIdYes

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?

Annotations already flag destructiveHint=true, but the description earns its keep by explaining exactly what is destroyed: submit=true is final, sent to the company, and cannot be taken back. It adds a content rule (candidate's own words, never invented facts), a validation behavior (rejects questionIds not on the candidate's matches), and a privacy/logging disclosure not present in the structured fields.

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 tight paragraphs, front-loaded with the action, then the safety-critical workflow, then the constraint. Nearly every sentence earns its place; the final privacy sentence is boilerplate but arguably required disclosure rather than filler.

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 destructive, irreversible mutation tool this covers the essential concerns: irreversibility, confirmation workflow, content integrity, validation failure mode, and data provenance. With an output schema present, it does not need to describe return values.

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 real meaning beyond the schema for submit: the schema only says it 'submits it,' while the description explains the draft-then-confirm workflow and the irreversibility. The answer parameter's provenance ('candidate's own words') is reinforced rather than merely repeated; questionId provenance is already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: 'Save the candidate's answer to one of a company's role questions,' and names listMatches/readMatch as the source of the questionId, which separates it from generic answer tools. It stops short of differentiating itself from editApplicationAnswer, a sibling an agent could plausibly confuse with it, so it is not a full 5.

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 gives a concrete workflow: draft first (submit=false), read the answer back, confirm with the candidate, then submit. It also routes the agent to listMatches or readMatch to obtain the questionId. What it lacks is an explicit statement of when this tool is preferred over the answer-editing alternative.

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