ask-aayan
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOOKING_URL | No | An https: URL that the book_call tool returns as a scheduling link. If unset, book_call returns a mailto: link with the subject filled in. |
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 answers questions about Syed Aayan Ahmed (AI & Automation Engineer) from his CV and portfolio. Answer only from tool results. Do not add facts from memory or guess. If no tool result covers the question, say it is not in his profile and offer his contact details from get_contact. Start with get_summary for an overview, search_profile for a specific topic, get_availability for dates, get_contact or book_call to reach him.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_summaryA | Overview of Syed Aayan Ahmed: headline, target role, location, current job, profile paragraph, languages and his one belief about the work. Call this first for any general question about him. |
| get_experienceA | His jobs, newest first, with dates, location and what he built in each. Filter by company (e.g. "Teamworks") or by a skill or technology (e.g. "n8n", "LDAP"). Use for questions about where he worked and what he did there. |
| get_projectsA | Projects he built (production work, personal R&D, university), each with what it does, his role, results and stack. Filter by tag, e.g. "voice", "extraction", "on-prem", "automation", "rag". Use for "what has he shipped" questions. |
| search_profileA | Keyword search across his whole profile (summary, jobs, projects, lab demos, education, skills, availability, contact). Returns matching snippets labelled with their section. Use for a specific technology, domain or claim that the other tools do not answer directly. |
| get_skillsB | His skills grouped as on his CV (AI & LLM, Automation & Integration, Software Engineering, DevOps & Cloud, Data & ML, Ways of working) plus spoken languages with levels. |
| get_availabilityA | When he can start: current role, graduation date, and from when he is available full-time. Pass a month (YYYY-MM) to get a yes/no for that month, e.g. "2027-03" for March 2027. |
| get_contactA | How to reach him: email, LinkedIn, GitHub, portfolio, a link to his CV as PDF, and his location. Use when someone wants to contact him or see his CV. |
| book_callA | Gives a link to set up a call with him: his scheduling page if one is configured, otherwise an email link with the subject filled in. Use when someone wants to talk to him. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| screen-candidate | Structured screening of Syed Aayan Ahmed against a job description: fit summary, evidence per requirement, gaps and questions, using only this server's tool results. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| cv-en | His full CV in English, as Markdown. |
| cv-de | His full CV in German, as Markdown. |
TDQS
Scored across 8 tools
Each tool maps to a distinct profile section (summary, experience, projects, skills, availability, contact, scheduling), so selection is mostly obvious. The only soft overlap is search_profile, which spans all sections, but it is explicitly framed as the fallback for specifics the targeted tools do not cover.
All eight tools follow a clean verb_noun snake_case pattern (get_summary, get_experience, search_profile, book_call). The verb varies (get/search/book) but the convention is uniform and predictable.
Eight tools is well within the sweet spot for a personal-profile server, and each one covers a distinct section or action with no filler. Nothing feels padded or missing at the count level.
The surface covers the full lifecycle of a profile query: overview, experience, projects, skills, availability, contact, scheduling, plus keyword search as a catch-all. Education and lab demos are only reachable via search_profile, a minor gap an agent can work around.