Priya Gautam MCP Server
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-profileA | Get a compact overview of Priya Gautam's profile, skills, experience, projects, and MCP compatibility. |
| get-skillsB | Get Priya Gautam's technical skills and technology stack. |
| get-projectsA | Get Priya Gautam's major software projects and their technologies. |
| get-educationB | Get Priya Gautam's education details. |
| get-experienceB | Get Priya Gautam's professional experience. |
| list-sectionsB | List the profile sections that the DCR engine can retrieve. |
| search-priya-profileB | Search Priya Gautam's professional profile using Dynamic Context Retrieval (DCR). Use this tool whenever the user asks about Priya Gautam's education, skills, experience, projects, technologies, certifications, achievements, or professional background. |
| search-profileB | Search Priya Gautam's profile using Dynamic Context Retrieval (DCR). Use it for questions about her education, skills, experience, projects, technologies, certifications, or background. |
| explain-dcrC | Explain how this server applies Dynamic Context Retrieval to Priya Gautam's profile. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| introduce-assistant | Create a short intro suitable for an MCP client. |
| answer-about-me | Use the assistant profile to answer a question about the assistant. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| profile | |
| sections | |
| dcr |
TDQS
Scored across 9 tools
There is significant overlap: get-profile, get-skills, get-projects, get-education, and get-experience provide section-specific data, but search-priya-profile and search-profile are near-duplicates both using DCR to search the entire profile. Agents could easily misselect between search-priya-profile and search-profile, and between the individual getters and search tools when a broad query comes in.
Most tools follow a clear get-<section> pattern (get-profile, get-skills, get-projects, get-education, get-experience) and list-sections, but search-priya-profile breaks the pattern by embedding the person's name instead of using a consistent 'search-<target>' prefix like search-profile does. The inconsistency between the two search tool names is the main deviation.
9 tools is a reasonable count for a profile server, but the surface feels padded: search-priya-profile and search-profile appear to be redundant duplicates serving the same purpose, and explain-dcr is more documentation than a functional tool. The effective distinct tool count is closer to 6-7.
The server covers profile sections well (skills, projects, education, experience, plus a compact overview). Minor gaps exist, such as no dedicated tools for certifications or achievements despite those being mentioned in search descriptions, but the search tool can still surface that data.