Skip to main content
Glama

BRAINIAC Recruitment Operations

Draft interview questions

recruitment-operations_interview-question-generate
Read-onlyIdempotent

Draft questions from missing required items, inferred alias matches, and job responsibilities. The questions do not score the candidate. Price $0.04 USDC. POST /api/v1/recruitment-operations/interview-question-generate. An unpaid call returns the x402 payment terms and does not run.

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": {
      "candidate": "<candidate>"
    },
    "name": "recruitment-operations_interview-question-generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNotitle, string, length 1 to 200. Optional.
aliasesNoaliases, array. Optional.
jobTextNojobText, string, length 1 to 20000. Optional.
candidateYescandidate, object. Required.
requirementsNorequirements, array. Optional.

Output Schema

NameRequiredDescriptionDefault
issuesNoissues. Array.
statusNostatus. String.
checkedAtNocheckedAt. String.
questionsNoquestions. Array.
limitationsNolimitations. Array.
candidateRefNocandidateRef. String.
hiringDecisionNohiringDecision. Boolean.
qualificationsInventedNoqualificationsInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses non-trivial operational behavior: the $0.04 USDC price, the POST endpoint, and critically that an unpaid call returns x402 payment terms rather than executing. That payment-gating behavior is exactly the kind of context annotations cannot convey. It does not describe the shape or volume of generated questions, which is partly covered by the output schema.

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?

Four short sentences, front-loaded with the core purpose and the non-scoring caveat before the commercial and transport details. Every sentence carries information; the endpoint path largely restates the tool name but is arguably useful for direct HTTP callers. No filler or hedging.

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 deeply nested five-parameter tool with an output schema and full schema coverage, the description covers the pieces structured data cannot: no scoring, pay-per-call pricing, and payment-gate failure mode. Remaining gaps are minor - how many questions are produced and how conflicts between requirements and candidate data are handled.

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 description coverage is 100%, so the baseline is 3. The description does add some semantic mapping - 'missing required items' points at the requirements array, 'inferred alias matches' at aliases, and 'job responsibilities' at jobText/requirements.kind=responsibility - but it does not explain how candidate or title influence the output, nor how aliases resolve to requirements.

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 names a specific verb and resource ('Draft questions') plus the three inputs they are derived from (missing required items, inferred alias matches, job responsibilities). It also draws a boundary against scoring siblings by stating 'The questions do not score the candidate'. Sibling differentiation is present but partial - it only distinguishes itself from ranking/scoring tools, not from resume-data-extract or job-description-structure.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the stated input sources: you would call this when you have requirements, aliases and job text and want gap-driven questions. There is no explicit when-to-use or when-not-to-use guidance and no named alternative sibling to route to. The 'does not score' note helps exclude one alternative but no positive routing rule is given.

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