get_context
Retrieves project-specific coding standards, guardrails, and workflow for the given task to ensure compliance and avoid anti-patterns.
Instructions
Returns coding standards, guardrails, and workflow for implementing a task.
WHEN TO USE:
ALWAYS call this FIRST before writing any code
When starting a new feature, bugfix, or refactor
When unsure about project conventions
RETURNS:
Detected stack (Java/Python/TypeScript/Go/Rust/etc)
Task type classification (feature/bugfix/refactor/test/security/performance)
MUST rules (mandatory guidelines)
AVOID rules (anti-patterns to prevent)
Code quality thresholds (max lines, coverage %)
Naming conventions (classes, methods, files)
Recommended TDD workflow
EXAMPLE: get_context({ task: "Create payment service", project_dir: "/path/to/project" })
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"task": "<task>"
},
"name": "get_context"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task | Yes | What you're implementing (e.g., "Create payment service", "Fix login bug") | |
| project_dir | No | Project directory for auto-detection of stack and .corbat.json config (optional) |