Analyzes code using Karpathy's principles to promote simplicity, surgical changes, and goal-driven execution. Prevents common coding mistakes.
Review code against the 4 Karpathy principles: Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | The code snippet to review | |
| context | No | Optional context about what the code is supposed to do |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, description does not disclose whether this tool modifies state, requires permissions, or returns a report. Minimal behavioral info.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with front-loaded verb and resource list. Efficient but could benefit from structured outcomes.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, description omits what the review result looks like (e.g., comments, pass/fail). Incomplete for single-param tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, baseline 3. Description adds no extra meaning beyond schema's parameter descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States verb 'Review code' and resource '4 Karpathy principles', distinguishing from sibling 'get_guidelines' which likely returns guidelines.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool over sibling 'get_guidelines'. No when-not or prerequisites mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Yangleduo00337788/Karpathy-Guidelines-MCP-Server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server