Overview
The server exposes read tools for profile lookups and optional mutation tools for workflows that create data.- Read tools are marked
readOnlyHint: trueandidempotentHint: true. - Mutation tools are marked
readOnlyHint: falseandidempotentHint: false. - All tools keep
destructiveHint: falseandopenWorldHint: true.
structuredContent.data.
Example tool result envelope
Read tools
get_candidate
Gets the top-level candidate profile.
Input: none
Related REST endpoint: GET /candidate
list_experience
Lists experience entries. You can optionally filter the response to current or past roles.
Input
currentis optional.- Use
trueto request current roles only. - Use
falseto request past roles only.
GET /experience
get_experience
Gets one experience entry by id.
Input
GET /experience/{id}
list_projects
Lists project summaries.
Input: none
Related REST endpoint: GET /projects
get_project
Gets one project by id.
Input
GET /projects/{id}
get_availability
Gets the current availability status.
Input: none
Related REST endpoint: GET /availability
get_resume
Gets the resume as structured JSON or as a PDF link payload.
Input
formatacceptsjsonorpdf.- The default is
json.
GET /resume
Optional mutation tools
create_auth_token
Creates a demo bearer token for the Candidate Profile API and triggers the API’s email notification flow.
Input
POST /auth/token
create_contact
Submits a contact request through the Candidate Profile API.
Input
POST /contact