Skip to main content
Glama
Sign In
dev-env-setup

dev-env-setup

by cmwen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

check_environment

Check which development tools are installed on your system, including Python, Node.js, Flutter, Android, Git, and Docker.

Instructions

Check which development tools are currently installed on the system (Python, Node.js, Flutter, Android, Git, Docker, etc.)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Check' implies a read-only operation, which is a useful behavioral hint, but it does not explicitly state that no changes are made or that it is safe to run. It also does not describe output format or any side effects, leaving some ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that is front-loaded with the core action ('Check which development tools...') and includes helpful examples. Every word earns its place, with no redundant information or filler.

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

Completeness5/5

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

This is a simple read-only tool with no parameters and no output schema. The description fully explains what it checks and provides a clear list of example tools. In the context of sibling install tools, the purpose is self-evident, and no further detail is necessary for an agent to select and invoke it correctly.

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 schema has zero parameters, so schema coverage is trivially 100%. The description adds no parameter details, but none are needed. The tool requires no user input, and the description appropriately focuses on the tool's purpose rather than parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool checks for installed development tools, listing specific examples (Python, Node.js, etc.). This distinguishes it from sibling tools like install_* tools, which perform installations, and get_system_info, which likely focuses on broader system information.

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 description provides no explicit guidance on when to use this tool versus alternatives. It does not mention that it should be used before installing tools to check existing installations, nor does it contrast with get_system_info or install_* tools. Usage is only implied, not stated.

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

Deploy Server

Other Tools