Skip to main content
Glama

Extract CV fields: experience, education and skills

resume_parse
Read-only

Structured data from a CV or resume: name, contact details, location, links, summary, skills, languages, certifications, work experience and education, with null or empty lists where the text has nothing. Plain text, or a PDF with a text layer by URL or base64. Dates are kept as written. Price: $0.005 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "resume_parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNohttps link to a PDF CV with a text layer (JSON body field)
textNoThe CV text (JSON body field); or give url or pdf_base64 instead
pdf_base64NoThe PDF as base64, up to 15 MB (JSON body field)

Output Schema

NameRequiredDescriptionDefault
modelNo
resumeNo
sourceNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses real behavioral traits: null or empty lists where no data exists, dates preserved as written, input size limit context, and a pricing model ($0.005 per successful call via x402 on USDC/Base/Solana, failed calls uncharged). Not stating what happens on an OCR-less scanned PDF or timeout behavior keeps it from a 5.

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?

Two dense sentences, with the extracted-field inventory front-loaded and the input formats and pricing following in logical order. The long field list is slightly list-heavy but every item earns its place by telling the agent what comes back.

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?

With an output schema present, the description need not explain return shape, and it instead covers the things structured fields cannot: input format alternatives, null/empty-list semantics, date preservation, and billing. Only failure modes for non-text-layer PDFs are left unaddressed for a tool whose whole premise is text-layer PDFs.

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 the schema already explains that url, text and pdf_base64 are mutually exclusive alternatives. The description's restatement ('Plain text, or a PDF with a text layer by URL or base64') reinforces the choice but adds no new syntax or constraints, so the baseline of 3 applies.

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 gives a specific verb+resource ('Structured data from a CV or resume') and enumerates the extracted fields: name, contact details, location, links, summary, skills, languages, certifications, work experience, education. It is clearly distinct from siblings like invoice_extract or extract by the narrow CV resource, though it never explicitly says so.

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 resource and accepted inputs ('Plain text, or a PDF with a text layer by URL or base64'), so an agent can infer when it applies. There is no explicit when-to-use/when-not framing, no statement about non-CV documents (e.g. invoices) or what to do if a PDF lacks a text layer beyond the implied failure.

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