Skip to main content
Glama

BRAINIAC Recruitment Operations

Rank a candidate shortlist

recruitment-operations_candidate-shortlist-rank
Read-onlyIdempotent

Score candidates only from explicit required matches. An exact match is worth 2 and a caller alias is worth 1. Ties keep the caller's order. Price $0.05 USDC. POST /api/v1/recruitment-operations/candidate-shortlist-rank. 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_candidate-shortlist-rank"
  }
}

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
titleNotitle. String.
issuesNoissues. Array.
statusNostatus. String.
factorsNofactors. Array.
checkedAtNocheckedAt. String.
candidatesNocandidates. Array.
limitationsNolimitations. Array.
hiringDecisionNohiringDecision. Boolean.
qualificationsInventedNoqualificationsInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses the exact scoring weights (2 for exact match, 1 for caller alias), the stable-sort tie policy, the $0.05 USDC price, and critically that an unpaid call returns the x402 payment terms without executing. That payment-gate behavior is the kind of detail annotations cannot convey and directly affects how an agent must sequence the call.

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?

Five short sentences, front-loaded with the scoring rule that determines output, followed by tie behavior, price, endpoint and failure mode. The raw POST path is the least valuable sentence but plausibly aids the x402 payment flow; nothing else is padded.

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?

Return values are covered by the output schema, and the description supplies what the schema cannot: scoring weights, tie-breaking, cost, and the unpaid-call contract. For a 5-parameter, read-only, idempotent scoring endpoint, an agent has enough to call it correctly and to handle the payment failure path.

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; the description earns above that by explaining the semantics of the aliases parameter (a caller alias is worth 1 point) and implying that the candidates array order determines tie resolution. It still says nothing about how requirements[].strength of "preferred" is treated, which is the main semantic ambiguity left.

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 states a concrete verb and resource ("Score candidates") and constrains the scope to "explicit required matches," which separates it from a general match tool like resume-job-match. It never names a sibling, so an agent must infer the boundary from the title and scoring rule rather than being told.

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 scoring rule and tie-breaking behavior, so an agent can tell this is for ordering a shortlist against requirements. There is no explicit statement of when to choose this over candidate-skill-compare or resume-job-match, and no stated prerequisites beyond candidates being required.

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