ask-habib-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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_publicationsA | List all publications as id/title/venue/year records (JSON). |
| get_publicationA | Return the full record (title, venue, year, summary) for one publication id such as 'p3' (JSON). |
| search_publicationsA | Keyword-search publications over titles, summaries and venues (JSON). Example queries: 'deepfake', 'federated', 'vision transformer'. |
| get_profileA | Return Habib Ur Rehman's CV summary: bio, current role, education, skills, research interests, and contact links (JSON). |
| get_linksA | Return contact links: GitHub, LinkedIn, website, email (JSON). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| habib_cv | Habib Ur Rehman's profile as a Markdown CV. |
TDQS
Scored across 5 tools
list_publications, get_publication, and search_publications have clearly distinct retrieval semantics (enumerate vs. fetch-by-id vs. keyword query), so an agent can pick correctly. The only soft overlap is get_profile vs. get_links, since get_profile's description already promises 'contact links' that get_links also returns.
Every tool follows the same verb_noun snake_case pattern (list_/get_/search_ + resource). Resource nouns are used consistently and predictably across the set.
Five tools is a tight, well-scoped surface for a personal publications/CV server; each tool covers a distinct access pattern and none appears redundant enough to remove.
The read-only domain (browse, fetch, search publications; profile and links) is fully covered with no dead ends. Minor gaps: no filtering/listing by venue or year, and get_links largely duplicates contact data already in get_profile.