Zain Ahmed Platform MCP Server

get_skills

Read-only

Use this tool when inspecting Zain Ahmed's categorized technology stack across Multi-Cloud, Kubernetes, Infrastructure as Code, DevSecOps, Observability, and Agentic AI. Returns a dictionary of skill categories and tool lists.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_skills"
  }
}

Input Schema

Name	Required	Description	Default
`category`	No	Skill category: all, multiCloud, containersAndOrchestration, infrastructureAsCode, ciCdAndGitOps, agenticAiAndMlOps, observabilityAndSre, securityAndCompliance, programmingLanguages

Output Schema

Name	Required	Description
`multiCloud`	No	Multi-cloud platforms and services
`observabilityAndSre`	No	Monitoring, tracing, and SRE telemetry stack
`infrastructureAsCode`	No	Infrastructure as Code and GitOps tooling
`securityAndCompliance`	No	DevSecOps and compliance engineering tools
`containersAndOrchestration`	No	Kubernetes and container orchestration stack

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the result is a dictionary of categories to tool lists, plus the topical scope, but says nothing about the default behavior when no category is supplied or how the filter narrows results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the usage trigger and followed by the return shape. No filler, though the long category list in the first sentence is somewhat verbose relative to the value it adds.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple read-only getter with one optional parameter, full schema coverage, an output schema, and safety annotations. The description covers purpose, scope, and return shape adequately; only the no-category default behavior is unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single optional 'category' parameter already lists its accepted values, so the schema does the heavy lifting. The description's enumeration of categories loosely mirrors those values but adds no syntax, default, or behavior information beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('Zain Ahmed's categorized technology stack') and verb ('inspecting'), and enumerates the coverage areas (Multi-Cloud, Kubernetes, IaC, DevSecOps, Observability, Agentic AI). It clearly differs from get_profile/get_about-style siblings by being about skills specifically, though it does not explicitly contrast with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this tool when inspecting...' gives a usage context but no explicit when-not conditions or named alternatives among the many sibling getters. The agent must infer that this is the skills-specific reader rather than one of get_about, get_profile, or get_certifications.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Zain Ahmed Platform MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?