Skip to main content
Glama

BRAINIAC Recruitment Operations

Match a resume to a job

recruitment-operations_resume-job-match
Read-onlyIdempotent

Compare supplied skills, qualifications, and role dates with explicit required items. A caller alias is marked inferred. A responsibility is not marked met. Price $0.05 USDC. POST /api/v1/recruitment-operations/resume-job-match. 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_resume-job-match"
  }
}

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
scoreNoscore. Number.
titleNotitle. String.
issuesNoissues. Array.
statusNostatus. String.
matchesNomatches. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
candidateRefNocandidateRef. String.
hiringDecisionNohiringDecision. Boolean.
qualificationsInventedNoqualificationsInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior, so the bar is lower. The description still adds genuinely useful context the annotations do not: a $0.05 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing. The matching rules (aliases marked inferred, responsibilities never marked met) further disclose result semantics.

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?

The comparison behavior is front-loaded and the payment/endpoint details follow in short, waste-free sentences. The two middle sentences ('A caller alias is marked inferred. A responsibility is not marked met.') are telegraphic and read as fragments, which slightly hurts readability but not length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 values need not be explained, and payment behavior is well covered. However, for a nested five-parameter matching tool the description leaves open how jobText interacts with requirements and what happens when requirements is omitted, which is a meaningful gap for correct invocation.

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 adds a little meaning by explaining how aliases and responsibility-type requirements are treated in the comparison, but it does not clarify the relationship between jobText and requirements or how role dates are used. That is marginal value over the schema.

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 opens with a specific verb and resource set: 'Compare supplied skills, qualifications, and role dates with explicit required items.' That is clearly a matching/scoring operation and is distinguishable from siblings like resume-data-extract or candidate-skill-compare. It stops short of naming a sibling or stating the output shape, 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The phrase 'with explicit required items' hints that the caller must supply requirements, but the schema marks requirements as optional, so the agent gets no reliable routing signal. Usage is only implied.

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