Skip to main content
Glama

Project Info

project_info

Retrieves current project environment details from a specified root directory, helping AI assistants understand the workspace before onboarding, session management, or code verification.

Instructions

Get information about the current project environment.

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

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.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the one-liner — no indication that it is a read-only, side-effect-free operation, no note that it works against the current working directory or an explicit path, and no caveats about what happens if the path is not a project. With an output schema present the return shape is covered elsewhere, but the operational behavior is not.

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?

A single short sentence with no filler and nothing buried, so it is structurally clean and front-loaded. The terseness is a symptom of under-specification rather than of padding, which is why it does not drop further.

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

Completeness2/5

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

For a tool sitting in a large set of overlapping "get info about the project/context" siblings, the description is too thin to be actionable — an agent cannot tell what it will actually receive or when to prefer it. The existing output schema removes the need to describe return values, but the scope, data source, and sibling positioning are all missing.

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?

There is one optional parameter with 100% schema description coverage ("Project root directory.", default "."), so the schema already fully documents it and the baseline is 3. The description adds nothing about how the path affects the result — e.g. whether it is resolved relative to cwd or what happens for a non-project directory.

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

Purpose3/5

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

The description has a verb and a resource ("Get information about the current project environment"), but "information" and "environment" are left undefined — it never says whether this returns the project root, detected language/stack, git status, or config. It is not differentiated from close siblings such as get_context, project_dashboard, or file_info, so an agent cannot reliably pick it.

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?

There is no when-to-use guidance at all: no trigger conditions, no prerequisites, and no mention of the alternatives in the sibling set (get_context, project_dashboard, file_info). The agent must infer both the situation and the choice from a single generic sentence.

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