Skip to main content
Glama

BRAINIAC Recruitment Operations

Report a recruitment pipeline

recruitment-operations_pipeline-report
Read-onlyIdempotent

Combine the job requirements, resume facts, match explanations, experience checks, interview prompts, and shortlist scores. The report is not a hiring decision. Price $0.12 USDC. POST /api/v1/recruitment-operations/pipeline-report. 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": {
      "candidates": "<candidates>"
    },
    "name": "recruitment-operations_pipeline-report"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
gapsNogaps. Array.
titleNotitle. String.
issuesNoissues. Array.
statusNostatus. String.
factorsNofactors. Array.
matchesNomatches. Array.
overlapsNooverlaps. Array.
checkedAtNocheckedAt. String.
questionsNoquestions. Array.
candidatesNocandidates. Array.
limitationsNolimitations. Array.
hiringDecisionNohiringDecision. Boolean.
requirementCountNorequirementCount. Number.
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?

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, but the description adds information the annotations cannot convey: the price ($0.12 USDC), the endpoint, and critically that an unpaid call returns x402 payment terms and does not execute. That failure mode is exactly the kind of behavioral detail an agent needs before calling. It does not describe latency or how partial inputs are handled, keeping it below a 5.

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 sentences, front-loaded with what the tool produces, then the scope caveat, then the payment mechanics. The opening list is long but each element maps to a real sibling output, and the endpoint string is arguably redundant with the tool name though genuinely useful for a priced API call.

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?

With an output schema present, the description need not explain return values, and it covers the two things structured fields cannot: the cost and the unpaid-call behavior, plus the explicit 'not a hiring decision' caveat. The main remaining gap is guidance on sequencing relative to the sibling analysis tools.

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 parameters (title, aliases, jobText, candidates, requirements) are already documented in the schema. The description's enumeration of 'job requirements' and 'resume facts' loosely maps to the requirements and candidates inputs, but it adds no format, constraint, or interaction detail beyond that. Baseline 3 applies.

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 concrete output — a pipeline report that combines job requirements, resume facts, match explanations, experience checks, interview prompts, and shortlist scores — which effectively distinguishes it from the single-purpose siblings like candidate-skill-compare or interview-question-generate. The verb 'Combine' is slightly generic for what is really a report-generation/aggregation step, so it stops short of a 5.

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?

Aggregation of the sibling artifacts implies this tool is invoked after the individual analysis steps, and 'The report is not a hiring decision' scopes its role. However, there is no explicit when-to-use statement, no statement of prerequisites (e.g., that candidates/requirements must be supplied), and no exclusion of alternatives beyond the implicit framing.

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