Interactions

Built-in prompt

The server registers one prompt template: candidate_profile_summary.

It accepts one argument:

Args

{
  "focus": "general"
}

focus accepts general, experience, projects, or resume.

The default is general.

The prompt asks the client to summarize Jonah Anderson’s profile by using the available candidate tools.

Prompt output

The prompt returns one user message. The message text changes slightly based on focus.

Summarize Jonah Anderson's candidate profile using the available candidate tools.

Summarize Jonah Anderson's projects using the available candidate tools.

Prompt support varies by client. If your client does not surface MCP prompts directly, you can still ask the same task in plain language and let the client choose the tools.

Example interactions

Recruiter summary

Start with a broad task instead of naming endpoints.

Prompt

Summarize Jonah Anderson for a backend platform engineering role. Include current availability and the projects that best support the fit.

A client will usually reach for a small set of read tools.

Typical tool flow

get_candidate
get_availability
list_projects
get_project({ "id": "<selected project id>" })
get_project({ "id": "<selected project id>" })

Current experience only

Ask for filtering when you want the response to stay tight.

Prompt

Show Jonah Anderson's current roles only and explain the main responsibilities in plain language.

Typical tool flow

list_experience({ "current": true })

Resume handoff

Use the server when you need structured resume data and a shareable PDF link.

Prompt

Get Jonah Anderson's resume as structured data, then give me the PDF link as well.

Typical tool flow

get_resume({ "format": "json" })
get_resume({ "format": "pdf" })

Built-in MCP prompt

If your client exposes MCP prompts, start with the registered summary template.

Prompt args

{
  "focus": "projects"
}

That prompt asks the client to summarize Jonah Anderson’s projects by using the available candidate tools.

What to expect from clients

Some clients inspect resources first. Others go straight to tools.

Clients may paraphrase results instead of showing raw JSON unless you ask for the original data.

Optional mutation tools may be absent when the deployment disables them.

candidate-profile://profile/resume/pdf returns JSON that contains a PDF URL. It does not stream the PDF file itself.

Review all tools

See every read tool, optional mutation tool, and related REST endpoint in one place.

Overview

Resources

Tools

Interactions

Built-in prompt

Prompt output

Example interactions

What to expect from clients

Review all tools

​Built-in prompt

​Prompt output

​Example interactions

​What to expect from clients

Review all tools

Built-in prompt

Prompt output

Example interactions

What to expect from clients