Skip to main content
Glama

list_projects

Read-onlyIdempotent

Lists recent project files with path, name, style, and open time, plus the current file and unsaved changes status. Use the returned path with open_project.

Instructions

Read-only: the person's recent project files (path, name, style, when opened, whether the file still exists), and which file is open now and whether it has unsaved changes. Use a path with open_project.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description reinforces "Read-only" and adds behavior the annotations cannot convey. Notably it discloses that entries may be stale ("whether the file still exists") and that current-document state, including unsaved changes, is reported. It does not state ordering, count limits, or recency window, which would have pushed it higher.

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?

Two sentences, front-loaded with the read-only guarantee, then a tight parenthetical enumerating return fields, then the handoff to open_project. No filler and no repetition of the tool name.

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?

There is no output schema, so the description must carry the return-value burden itself, and it does: it lists the per-file fields and the current-document/unsaved-changes signal. For a zero-parameter read tool with full annotation coverage, nothing an agent needs in order to call it correctly is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly signals a no-argument call by never implying any filtering or scoping input.

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+resource (list the person's recent project files) and enumerates exactly what is returned: path, name, style, when opened, existence, plus the currently open file and its unsaved state. That is far more specific than a restatement of the name. It stops short of explicitly differentiating itself from get_project or edit_project, so a 4 rather than 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 Guidelines4/5

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

"Use a path with open_project" gives a concrete follow-on action that ties this listing tool to its sibling, so the agent knows what the returned paths are for. There is no explicit when-not guidance (e.g. versus get_project for a single known project), which keeps it from a 5.

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