kodekloud-mcp

Overview Schema Source Related Servers Discussions Admin

get_engineer_profile

Fetch KodeKloud Engineer career metrics—role, XP, global rank, tasks completed/failed, success rate, and promotion eligibility—to assess your standing.

Instructions

Retrieve user profile, career track level, XP, and rank on KodeKloud Engineer.

Returns current engineering role (e.g. 'DevOps Engineer', 'System Administrator'), total points/XP, global leaderboard rank, tasks completed, tasks failed, success rate, and promotion eligibility.

Returns: EngineerProfileResponse with standing and career metrics.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Error message if the operation or upstream request failed.
`warning`	No	Diagnostic warning or configuration guidance message.
`username`	Yes	KodeKloud Engineer username or handle.
`next_level`	No	Next role in career progression path (e.g. 'Senior DevOps Engineer').
`global_rank`	No	Position on the global leaderboard.
`streak_days`	No	Consecutive daily task completion streak.
`tasks_failed`	No	Total failed or expired tasks.
`total_points`	Yes	Total cumulative XP/points earned.
`current_level`	Yes	Current engineering role/level (e.g. 'DevOps Engineer', 'System Administrator').
`tasks_completed`	No	Total successfully validated tasks.
`success_rate_percent`	No	Success rate percentage (0.0 to 100.0).
`eligible_for_promotion`	No	Whether learner meets criteria to advance to the next level.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 1, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Retrieve' implies a read-only operation and the text enumerates the data returned, but it says nothing about authentication requirements, whose profile is fetched (self vs arbitrary user), or any rate/permission constraints.

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?

Front-loaded with the core action and resource, and reasonably short. The trailing 'Returns:' block restates the return fields a second time after already listing them, which is mild redundancy rather than harmful bloat.

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?

With an output schema present, the description need not explain return values, yet it is complete enough for an agent to call a zero-parameter read tool correctly. The main omission is the absence of any usage/routing context relative to its siblings.

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

Parameters4/5

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

The tool takes zero parameters, so the schema has no semantics to document and the baseline of 4 applies. There is no parameter ambiguity for the description to resolve.

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?

States a specific verb+resource ('Retrieve user profile, career track level, XP, and rank on KodeKloud Engineer') and scopes the domain to the Engineer track. It does not name any sibling tool, so the boundary versus get_learning_summary or get_course_progress is left to inference, but the purpose itself is unambiguous.

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?

No explicit when-to-use, prerequisites, or alternatives are given. The narrow scope ('on KodeKloud Engineer', profile/rank/XP metrics) lets an agent infer it is the tool for viewing one's own engineering standing, but there is no routing guidance against sibling metrics tools.

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

Deploy Server