Zain Ahmed Platform 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileB | Retrieve Zain Ahmed's verified professional profile, 5x multi-cloud credentials (AWS, Azure, GCP, OCI, HashiCorp), location, philosophy, and competencies. |
| get_skillsA | Retrieve complete categorised multi-cloud, Kubernetes, DevSecOps, IaC, and MLOps competency matrices with production seniority ratings. |
| get_certificationsA | Retrieve verified 5x multi-cloud credentials, badge verification URLs, and credential IDs across AWS, Azure, GCP, and OCI. |
| get_projectsA | List verified enterprise cloud architecture case studies, client domains, tech stacks, and quantifiable business outcomes. |
| get_articlesB | List in-depth architectural publications, SRE blueprints, and systems engineering deep dives. |
| search_knowledge_baseA | Full-text search across all case studies, architecture articles, developer documentation, and platform capabilities. |
| get_servicesA | Retrieve platform engineering advisory retainers, fractional leadership tiers, deliverables, commitments, and transparent rates. |
| calculate_finops_roiA | Calculate estimated cloud cost savings and ROI from Karpenter container bin-packing, spot orchestration, and Graviton migration. |
| submit_contactA | Dispatch an encrypted engineering inquiry or consultation request directly to Zain Ahmed with tracking reference ID. |
| search_docsA | Full-text search across all documentation, architectural blueprints, API guides, and system runbooks. |
| get_documentation_pageA | Retrieve full documentation content and guides for a specific platform topic. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Engineer Profile | Verified engineer bio, 5x cloud certifications, location, and contacts |
| Categorized Tech Stack | Full competency matrix across Multi-Cloud, Kubernetes, DevSecOps, IaC, and MLOps |
| Cloud Certifications Catalog | Verified AWS, Azure, GCP, and Oracle credential IDs and Credly verification URLs |
| Pricing Tiers and SLAs | Machine-readable engagement plans, SLAs, and transparent rates |
| OpenAPI 3.1 Specification | Complete OpenAPI 3.1.0 REST API specification in JSON format |
TDQS
Scored across 11 tools
Most tools are clearly distinct by resource type, but search_knowledge_base and search_docs have heavily overlapping scopes, and get_articles/get_documentation_page could be confused. Descriptions help resolve most ambiguities, but the search tool redundancy creates real selection risk.
The naming pattern is largely consistent with get_* for retrieval, search_* for search, and single action verbs for calculate/submit. Minor inconsistencies like search_docs vs search_knowledge_base and calculate_finops_roi not following a common verb prefix are small deviations from an otherwise clear scheme.
Eleven tools is reasonable for a personal platform covering profile, portfolio, services, documentation, search, ROI calculation, and contact. The count is not excessive, though the two overlapping search tools could be consolidated to make the surface tighter.
The server covers the main informational and engagement needs: profile, skills, certifications, projects, articles, services, documentation, ROI estimation, and contact. Minor gaps exist, such as no dedicated article detail retrieval action or project detail action, but agents can likely work around these via search and documentation tools.