Skip to main content
Glama

BRAINIAC Recruitment Operations

Validate candidate experience

recruitment-operations_candidate-experience-validate
Read-onlyIdempotent

Check supplied employment dates for invalid dates, overlaps, and gaps. Dates are not rewritten, and a gap is not a ranking penalty. Price $0.03 USDC. POST /api/v1/recruitment-operations/candidate-experience-validate. 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-experience-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidatesYescandidates, array. Required.

Output Schema

NameRequiredDescriptionDefault
gapsNogaps. Array.
rolesNoroles. Array.
issuesNoissues. Array.
statusNostatus. String.
overlapsNooverlaps. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
hiringDecisionNohiringDecision. Boolean.
qualificationsInventedNoqualificationsInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description discloses important behavior: dates are not rewritten, gaps are not treated as ranking penalties, the call costs $0.03 USDC, and an unpaid call returns x402 payment terms without running. These are meaningful operational details for a paid validation endpoint, though it does not elaborate further on validation outcomes because an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, followed by key behavioral caveats and payment details. Every sentence adds relevant information, and the endpoint and x402 gating are material for correct invocation.

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?

Given the output schema and rich annotations, the description supplies the validation scope, non-rewrite behavior, gap semantics, and payment gating needed to invoke it correctly. The detailed candidates payload is delegated to the schema, which is appropriate, though it could explicitly name the required input.

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% and there is one required 'candidates' array parameter. The description only clarifies that supplied employment dates are checked, without adding structure, date formats, or field-level meaning beyond what the schema already documents.

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?

The description states a specific verb ('Check') and resource ('supplied employment dates') plus the exact validation checks: invalid dates, overlaps, and gaps. It is clearly distinguishable from sibling tools like shortlist-rank, skill-compare, and resume-job-match because it focuses on date integrity rather than scoring or matching.

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?

The validation checks imply when the tool is useful, but the description gives no explicit when-to-use guidance versus alternatives or when-not-to-use conditions. It does clarify that a gap is not a ranking penalty, but that is behavioral context rather than usage routing.

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