Built-in prompt
The server registers one prompt template:candidate_profile_summary.
It accepts one argument:
Args
focusacceptsgeneral,experience,projects, orresume.- 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 onfocus.
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
Recruiter summary
Start with a broad task instead of naming endpoints.A client will usually reach for a small set of read tools.
Prompt
Typical tool flow
Current experience only
Current experience only
Ask for filtering when you want the response to stay tight.
Prompt
Typical tool flow
Resume handoff
Resume handoff
Use the server when you need structured resume data and a shareable PDF link.
Prompt
Typical tool flow
Built-in MCP prompt
Built-in MCP prompt
If your client exposes MCP prompts, start with the registered summary template.That prompt asks the client to summarize Jonah Anderson’s projects by using the available candidate tools.
Prompt args
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/pdfreturns 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.