Skip to main content
Glama

Read a resume

get_resume
Read-only

Get a specific resume by id, including all 12 editable sections (full_name, title, contacts, summary, experience, education, skills, projects, languages, interests, publications, references) plus the current visual style. Sections use the exact shapes and field names update_resume_section accepts, and every list entry carries an 'id' to echo back in edits. Returns 'not_found' if the resume does not exist or does not belong to the current user.

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": {
      "input": "<input>"
    },
    "name": "get_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
idYes
undoNoSet only by an edit that changed something: the versions around it.
styleNoCurrent visual style. Read-only here; change via set_resume_style.
titleNoProfessional title/headline (section: title).
skillsNo
summaryNo
contactsNo
languageNoLocale code the resume content is written in, e.g. en_EN. Not the spoken languages list.
projectsNo
educationNo
full_nameNoPerson's full name (section: full_name).
interestsNo
languagesNo
experienceNo
referencesNo
updated_atNo
resume_nameYesDocument name shown in list_resumes; change it via rename_resume, not update_resume_section.
publicationsNo
content_versionNoContent version of this read: a hash of the content, so equal content gives an equal version, also across copies. Entry ids belong to it; update_resume_section takes it as expected_content_version and answers 'resume_changed' once the resume has changed since.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / $defs / ResumeStyleInfo / properties / font / description
      Added value: +"Font pair: default is Inter (sans-serif) — a chosen font, not an unset one; classic is Lora, modern is Jost."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, non-open-world safety; the description adds real value beyond them by disclosing the returned payload structure, the presence of per-entry ids, and the 'not_found' outcome for missing or non-owned resumes. It does not mention pagination or size limits, but for a single-record read that is a minor gap.

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 sentences, front-loaded with the operation and then the payload contract, with the failure mode last. The 12-section enumeration is long but each item is informative, and nothing is obviously padded.

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?

For a single-record read with an output schema, the description supplies the contextual contract an agent needs: the full section list, stable ids for edits, visual style inclusion, and the not-found/ownership case. Return-value details overlap slightly with the output schema but do not detract from completeness.

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?

Only one parameter, and the schema already tells the agent it is a resume id returned by list_resumes; the description's 'by id' adds little on top of that. The useful extra semantic is the ownership constraint (a resume not belonging to the current user yields 'not_found'), which is more of a behavior than a parameter detail.

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?

States a specific verb and resource ('Get a specific resume by id') and enumerates what is returned: all 12 named sections plus the visual style. It does not explicitly separate itself from read-oriented siblings such as get_resume_revision or get_resume_history, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Implies a clear workflow by saying sections use the exact shapes update_resume_section accepts and that list entry ids should be echoed back in edits, which positions this as the read-before-edit call. It gives no explicit 'do not use this when...' exclusions or named alternatives, keeping it below a 5.

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.