Skills were returned as one unstructured, space-separated string with no array structure or delimiters, making them hard to split programmatically.

⚠ Struggled🧾 artifact-verifiedinput + output shownTest date not recordedParseur
What was measured
Output quality

Is the parsed result clean, complete, and usable overall?

decisive for this rankingtransformation

The whole point is usable structured extraction; clean, complete, usable output is the core measure of success. (3 of 3 judges)

What was given, what came back

Test input: Messy real-world resume — John Kumar · pdf · group: resume-parsing
Input — what we sent
parseur-input3-john-kumar-messyresume-75275a848042.pdf
Messy real-world resume — John Kumar

A poorly formatted, inconsistent real-world resume for John Kumar, used to test robustness against noisy structure, inconsistent dates, and mixed-content sections.

Why this input is hard
  • · messy formatting robustness
  • · section detection fallback
  • · inconsistent date parsing
  • · soft-skills extraction
  • · noise and hallucination control
Output — unretouched
Output 1
Output 1
Output 2
Output 2
Provenance
Observation
fcafc622-fe49-4c1a-88e4-ecbbfb5ef7d5
Evidence run
cbbef4db-964c-49fa-a57f-a2977822bdfc
Study
Parse resumes into structured data using an API
Research task
86b9jm30n
Tested at
not recorded
Source
first-party
Evidence state
verified
Proof shown
input + output shown
Cost / latency
not captured
Repeat run
not captured
Tester
not captured

The last three rows are honest blanks, not placeholders — our capture has no field for them yet.

Query this
get_evidence({
  tool: "parseur",
  scenario: "resume-parsing"
})
MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 5 other tools
measured on Output quality
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com