Skip to main content
Glama

BRAINIAC Recruitment Operations

Compare candidate skills

recruitment-operations_candidate-skill-compare
Read-onlyIdempotent

Compare supplied skill names across candidates and against an explicit skill list. Missing skills are not invented. Price $0.04 USDC. POST /api/v1/recruitment-operations/candidate-skill-compare. 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-skill-compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidatesYescandidates, array. Required.
skillNamesNoskillNames, array. Optional.

Output Schema

NameRequiredDescriptionDefault
issuesNoissues. Array.
statusNostatus. String.
overlapNooverlap. Array.
checkedAtNocheckedAt. String.
candidatesNocandidates. Array.
skillNamesNoskillNames. Array.
limitationsNolimitations. Array.
hiringDecisionNohiringDecision. Boolean.
qualificationsInventedNoqualificationsInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive, so the description's real contribution is the commercial and execution behavior: $0.04 USDC, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing. "Missing skills are not invented" also promises deterministic, non-hallucinated output, which is valuable context for a comparison tool.

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?

Sentences are short, front-loaded with purpose, and each carries distinct information (behavior, guarantee, price, transport, payment flow). The staccato endpoint/price fragments read as clipped rather than wasteful, so no sentence is removable.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers the remaining agent-relevant unknowns: cost, paid-vs-unpaid execution semantics, and the no-invention guarantee. For a 2-parameter read-only comparison tool, nothing needed to call it correctly is missing.

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 coverage is 100%, so the baseline is 3. The description maps loosely onto the two parameters (candidate records with skill entries, plus the explicit skill list), but adds no format, matching, or casing guidance for skill names beyond what the schema already provides.

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?

"Compare supplied skill names across candidates and against an explicit skill list" states a specific verb and resource, and the two-way comparison (candidate-vs-candidate and candidate-vs-requested list) separates it from siblings like resume-job-match. It stops just short of explicitly naming any alternative, so it is clear but not fully differentiated.

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 comparison framing implies when the tool is appropriate (skill-focused checks rather than full resume matching), but there is no explicit when-to-use or when-not-to-use statement and no named alternative among the siblings. Usage is inferable but must be inferred.

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