Skip to main content
Glama

Init Context

init_context

Scans project files to auto-detect tech stack, languages, and frameworks, initializing project context for AI-assisted onboarding and session management.

Instructions

Initialize or auto-detect project context. Scans project files to detect tech stack, languages, and frameworks.

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": "init_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the read/scan behavior but not whether the tool persists or overwrites existing context, whether it is idempotent, or what permissions/files it touches — significant gaps for a setup/mutation tool. The output schema covers return values, so that is not held against it.

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 short sentences with the core action front-loaded and zero filler. It is efficient, though the second sentence slightly repeats the 'detect' idea from the first rather than adding new information.

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

Completeness3/5

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

With one param, full schema coverage, and an output schema, the structural side is well covered. However, for a context-initialization tool with no annotations, the description omits critical operational details: overwrite/idempotency behavior, relationship to get_context and bootstrap_project, and whether the scan has side effects.

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?

One optional parameter ('path') with 100% schema description coverage, so the schema already explains its meaning. The description adds no default behavior, relative-vs-absolute path handling, or guidance on scanning a subdirectory, so the baseline 3 applies.

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 (initialize or auto-detect) and resource (project context), plus the mechanism (scanning project files for tech stack, languages, frameworks). It does not distinguish itself from close siblings such as get_context, update_context, or bootstrap_project, so it falls short of a 5.

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

Usage Guidelines2/5

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

The phrase 'Initialize or auto-detect' weakly implies a first-time setup scenario, but there is no explicit when-to-use guidance, no mention of running this before get_context/update_context, and no statement of what happens if context already exists. The agent must infer placement in the workflow.

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