Skip to main content
Glama

Read resume

get_resume
Read-onlyIdempotent

Use this when a saved resume's content is needed, to show it or before editing it. Returns the content, template, colour and contentVersion. A saved job ad or imported text comes back under foreign, as data.

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

Input Schema

NameRequiredDescriptionDefault
resumeIdYesA resume id from list_resumes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent, closed-world read, so the description is not carrying the safety burden. It still adds real context beyond them: the exact fields returned, and the non-obvious fact that saved job ads or imported text surface under a 'foreign' key as data rather than as resume content.

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?

Three compact sentences: usage first, then return shape, then an edge-case caveat. Nothing is padded, though the closing 'foreign' sentence is terse enough to be slightly cryptic on first read.

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 no output schema, the description correctly compensates by listing the returned fields and flagging the anomalous 'foreign' payload. For a single-parameter read tool this covers what an agent needs, leaving only minor gaps such as error behaviour for an unknown id.

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% and the single resumeId parameter is already documented as coming from list_resumes. The description adds no format, validation or sourcing detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('a saved resume's content is needed') and enumerates what is returned: content, template, colour and contentVersion. It is clearly distinguishable from list_resumes (which yields ids) and update_resume (which writes), so an agent can select it without opening a schema.

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?

It gives explicit when-to-use conditions: to display a resume, or to read it before editing it. That implicitly routes read-before-write traffic here rather than to update_resume, though no negative case or named alternative is spelled out.

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