Skip to main content
Glama

list_projects

List all tracked coding and non-coding projects for deep dives when the desk summary is insufficient.

Instructions

Full project roster. Prefer get_desk_summary first. Use this for a deep dive only.

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 observedv1.4.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden of behavioral disclosure, and it says almost nothing. It does not reveal how many projects might be returned, whether results are paginated, whether the response is expensive or slow, or what fields each roster entry contains. The word "Full" hints at unbounded volume but never confirms or bounds it.

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?

Three short sentences with no filler, and the routing advice is front-loaded after the one-line purpose. It is arguably over-compressed: the terse fragments leave real gaps rather than trimming redundancy.

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

Completeness3/5

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

With no parameters and no output schema, the description is the only place an agent can learn what a "project roster" entry looks like or what "deep dive" yields. It establishes routing but not the shape, size, or cost of the result, which is the main remaining question for a bulk-list tool.

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 the baseline is 4. There is nothing for the description to clarify, and it correctly presents this as an argument-free call.

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?

"Full project roster" names the resource and implies a complete listing, but there is no explicit verb and the phrase is a fragment rather than a stated action. It partially distinguishes itself from get_desk_summary by positioning this as the exhaustive variant, yet an agent must infer that this returns all projects.

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?

"Prefer get_desk_summary first. Use this for a deep dive only" explicitly names the sibling alternative and sets a clear ordering: start with the summary, escalate here. What is missing is any criterion for what makes a deep dive warranted (e.g., needing every project's metadata vs. an overview).

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