adrian-capraru-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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileA | Positioning, summary, every role with highlights and key figures, location and remote terms, what he is open to, languages, education, skills and links (site, CV PDF, LinkedIn, GitHub, Upwork). |
| list_case_studiesA | The 7 case studies on his site: slug, title, one-paragraph summary, headline figure and URL. Pass a slug to get_case_study for the full write-up. |
| get_case_studyA | One case study in full: client type, role, timeline, status, the problem, what was built, measured results, stack and links. |
| list_servicesA | Published offers: 12 fixed-price projects (3 tiers each, with delivery days and what is included) and 3 consultations. Prices are quoted on his Upwork profile or after a discovery call. |
| check_availabilityA | Current availability status, as he last set it, with the date it was updated, what he is open to and his time zone. A status note, not a booking calendar. |
| how_to_hireA | Contact routes: the site contact page, his Upwork profile, LinkedIn and the CV PDF, with what each route is for and what to include in a first message. This tool sends nothing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct role: browsing services, checking availability, listing or fetching case studies, getting contact routes, and retrieving the profile. The only minor overlap is that both check_availability and get_profile mention what Adrian is open to, but the descriptions make the boundary clear enough.
Most tools follow a predictable verb_noun pattern (list_services, check_availability, get_case_study, list_case_studies, get_profile). The one deviation is how_to_hire, which is a phrase rather than a verb_noun name, but it remains clear and readable.
Six tools is well-scoped for a personal professional profile server. Each tool covers a distinct area of information and none feels redundant or excessive.
The surface covers the core domain comprehensively: services, availability status, case study index and detail, hiring/contact routes, and full profile information. The explicit note that check_availability is not a booking calendar and how_to_hire sends nothing indicates intentional, non-dead-end boundaries.