Skip to main content
Glama

Get my career record

getCareerRecord
Read-onlyIdempotent

The career record the Me tab shows: roles, education, skills and languages Clera holds for the candidate, merged from their resume, LinkedIn, GitHub and what they entered, with the sources behind each entry, plus total months of experience. Read it before advising on their resume or explaining a match, and when they ask what Clera knows about them. It is read-only: preferences change through editPreferences, the resume through importResumeFromLink or the resume builder tools.

Clera privately records this tool's inputs and results for usage tracking and support.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
skillsYes
educationYes
languagesYes
experiencesYes
totalMonthsExperienceYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the description's 'read-only' restatement adds little on its own. It does contribute value annotations cannot: per-entry source provenance and a privacy/logging disclosure that inputs and results are recorded for usage tracking and support. It does not address freshness, i.e. how current the merged external data is, which is the main behavioral unknown for an aggregated record.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence front-loads what the record is and what it contains, the second gives usage triggers, and the third redirects mutations to the right tools. The long opening sentence is dense but every clause (sources, merges, months of experience) carries information an agent would otherwise have to discover by calling the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape need not be described, and annotations cover the safety profile; the description fills the remaining gaps by explaining data origin, provenance per entry, and when to reach for it. For a zero-parameter read tool, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to add; the baseline for a no-param tool applies. The description correctly does not waste space inventing arguments.

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 names the exact resource and enumerates its contents (roles, education, skills, languages, total months of experience) plus how it is assembled (merged from resume, LinkedIn, GitHub and manual entry, with sources per entry). That level of specificity lets an agent know precisely what comes back without opening the output schema, and the phrasing 'the career record the Me tab shows' gives a concrete mental model.

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

Usage Guidelines5/5

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

It states positive triggers ('read it before advising on their resume or explaining a match, and when they ask what Clera knows about them') and routes mutations to explicit alternatives (editPreferences for preferences, importResumeFromLink or the resume builder tools for the resume). Both when-to-use and when-not-to-use are covered, so nothing is left to inference.

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