Retrieve current terminal context—git branch, active venv, Node version, Docker status, and working directory—to inform commands and avoid environment mistakes.
Get current terminal environment context including git branch, active venv, node version, docker status, and working directory
| Name | Required | Description | Default |
|---|---|---|---|
| working_directory | No | Optional directory to check context for (defaults to current) |
Changes observed during successful MCP inspections.
v8.0.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral burden. It usefully discloses what the current context includes (git branch, venv, node version, docker status, working directory), but does not explicitly state that it is read-only, whether it can be slow when checking docker, or what the return structure looks like.
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?
The definition is a single front-loaded sentence that states the action and lists the relevant context fields without filler. Every element earns its place.
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?
With one optional parameter, no output schema, and no annotations, the description does a good job listing the returned context components. It could be more complete by stating the return shape or explicitly confirming the read-only nature, but the core information needed to call the tool is present.
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 description coverage is 100%, and the single optional parameter 'working_directory' is fully documented in the schema as defaulting to the current directory. The description adds no parameter-level detail beyond the schema, so baseline 3 is appropriate.
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?
The description gives a specific verb and resource ('Get current terminal environment context') and enumerates the exact context fields returned. It is clear what the tool does, though it does not explicitly differentiate itself from nearby tools like capture_environment or diff_environment.
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?
It implies usage by saying it retrieves current context, but gives no explicit guidance on when to use this tool versus capture_environment, diff_environment, or other environment-related siblings. There are no exclusions, prerequisites, or alternative-selection cues.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.