Skip to main content
Glama

list_projects

View all registered projects including chunk counts, quality scores, health stats, and git repo URLs. Check which projects exist and their index sizes.

Instructions

List all registered projects with chunk counts and health stats. Read-only.

    Use to check which projects exist, their index sizes, quality scores,
    and git repo URLs. Use get_active_project() to check only the active
    project for the current session.

    Returns:
        Per-project summary: name (with active marker), total chunks,
        quality score, docs path, and git repo URL if configured.
        Returns setup instructions when no projects are registered.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Despite no annotations, the description discloses it is read-only and specifies the return structure, including handling of the no-projects case. However, it lacks details on authentication or potential side effects, but for a listing operation this is sufficient.

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?

The description is concise, with two clear paragraphs. The first sentence immediately conveys purpose. No redundant information is present, but it could be slightly more succinct.

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?

The description explains the return values in detail, including the special case when no projects are registered. An output schema exists, so the description need not elaborate further. The tool is well-differentiated from its many siblings.

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?

There are no parameters, so the schema coverage is 100% trivially. The description does not add parameter-specific information, which is acceptable as none exist. Baseline 4 is appropriate.

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 lists all projects with specific details like chunk counts and health stats. It distinguishes itself from the sibling tool 'get_active_project' by explicitly noting the difference.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool (to check project existence, index sizes, etc.) and when to use the alternative 'get_active_project()' for checking only the active project.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dl4rce/flaiwheel'

If you have feedback or need assistance with the MCP directory API, please join our Discord server