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 with prices in USD: 12 fixed-price projects (3 tiers each, with delivery days and what is included) and 3 paid consultations. All are bought through his Upwork profile. |
| 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 targets a clearly distinct resource: profile, case study list/detail, service offers, availability status, and hiring routes. The list/get split for case studies is explicit, and the availability tool is explicitly framed as a status note rather than a booking calendar. Minor duplication of 'open to' in profile and availability is clarified by the descriptions.
Most names follow a readable snake_case verb_noun pattern: get_profile, list_case_studies, get_case_study, list_services, check_availability. The one deviation is how_to_hire, which is a phrase rather than a verb-led action, though it remains clear and consistent in casing.
Six tools is well-scoped for a personal professional profile server. Each tool covers a meaningful content area, and there are no redundant or filler tools.
The surface covers the natural read-only lifecycle for this domain: general profile, detailed case studies with list/detail access, priced services, current availability, and contact/hiring routes. No create/update/delete operations are expected for a published personal profile, and no obvious content area is missing.