nima-career-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileA | Return Nima Karami's public-safe profile: name, headline, location, links, bio. |
| list_rolesA | List every role/job (flat) with id, org, company_id, title, dates, tags. Roles sharing a company_id are a title progression at one company; use list_experience for the grouped view. |
| list_experienceA | Roles grouped into company tenures (newest first). Each company tenure lists its positions (title progression) newest-first. A company you left and later rejoined appears as two separate tenures. Use this when you want experience grouped by employer rather than as a flat list of titles. |
| get_roleA | Get one role in full, including its evidence bank and approved resume bullets. Use list_roles first to discover valid role ids (e.g. 'timeplay'). |
| list_projectsA | List projects, optionally filtered by tags (AND) and/or owning role_id. |
| get_projectA | Get one project in full: blurb, evidence, approved bullets, and links. |
| list_skillsC | List skills grouped by category; each skill links to backing evidence ids. |
| search_experienceB | Search across roles, projects, bullets, and skills. This is the main entry point for queries like "show me his 0-to-1 product work".
|
| list_bulletsA | List curated, hiring-manager-safe resume bullets. Each bullet is pre-approved and cites the evidence ids it derives from. Filter by role_id, project_id, and/or tags (AND). With no filters, returns all bullets. |
| assemble_resumeA | Assemble a tailored resume draft for a query (e.g. "backend-leaning"). SELECTS and ORDERS the most relevant approved roles, evidence, bullets, and skills
for Args: focus: free-text angle, e.g. "0-to-1 product" or "backend". role_ids / project_ids: pin specific items instead of ranking by focus. skill_categories: restrict the skills section. length: "full" or "onepage" (caps roles/bullets). format: "structured" (default) or "markdown" (also returns rendered markdown). The returned draft includes a |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| guidance | Honesty + anti-injection rules for hosts consuming this server. |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: assembling resumes, retrieving profile/project/role details, listing bullets/experience/projects/roles/skills, and searching across items. There is no ambiguity between tools.
All tools follow a consistent verb_noun snake_case pattern (e.g., assemble_resume, get_profile, list_roles, search_experience), making the API predictable and easy to navigate.
With 10 tools, the set is well-scoped for a career portfolio server. Each tool serves a necessary function without redundancy, fitting the typical 3-15 range perfectly.
The tool set covers all essential operations for the domain: retrieving profile, roles (flat and grouped), projects, bullets, skills, searching across items, and assembling a resume. There are no obvious gaps for a read-only portfolio server.