Skip to main content
Glama

BRAINIAC Recruitment Operations

Extract resume data

recruitment-operations_resume-data-extract
Read-onlyIdempotent

Read Skill, Role, and Qualification lines. Personal-attribute lines and references are ignored and are not stored. Price $0.04 USDC. POST /api/v1/recruitment-operations/resume-data-extract. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recruitment-operations_resume-data-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoid, string, length 1 to 80. Optional.
nameNoname, string, length 1 to 200. Optional.
textNotext, string, length 1 to 20000. Optional.
rolesNoroles, array. Optional.
skillsNoskills, array. Optional.
qualificationsNoqualifications, array. Optional.

Output Schema

NameRequiredDescriptionDefault
rolesNoroles. Array.
issuesNoissues. Array.
skillsNoskills. Array.
statusNostatus. String.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
candidateRefNocandidateRef. String.
hiringDecisionNohiringDecision. Boolean.
qualificationsNoqualifications. Array.
qualificationsInventedNoqualificationsInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful context beyond that: a $0.04 USDC cost, the x402 payment-terms failure mode for unpaid calls, and a privacy rule that personal-attribute lines and references are dropped and not stored. It omits any note on rate limits or processing behavior, so it is additive but incomplete.

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?

Four short, front-loaded sentences with no filler; the extraction scope comes first and operational caveats follow. The raw endpoint string is mildly redundant but the pricing sentence earns its place.

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?

With an output schema present, return values need not be explained, and cost plus data-handling are covered. However, with all six parameters optional and no indication of how text, name, id and the structured arrays interact, an agent still lacks enough to build a confident payload.

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 schema already documents all six parameters and their constraints; the baseline is 3. The description's mention of Skill/Role/Qualification lines loosely maps to the skills, roles and qualifications arrays but adds no syntax, precedence or input-source guidance (e.g. whether free text or the structured arrays drive extraction).

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 the exact line types it extracts (Skill, Role, Qualification) and gives the endpoint, so the operation is identifiable. It stops short of stating the output as a structured resume record or contrasting with siblings like resume-job-match, so an agent must infer the broader purpose.

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 when-to-use or when-not-to-use guidance and no mention of the sibling tools it might be chained with. The only behavioral routing is the payment caveat, which tells the agent nothing about choosing this tool over alternatives.

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