Skip to main content
Glama

list_projects

Retrieve projects registered through the CLI and their approved check configurations to inspect available workspaces and confirm which checks are enabled.

Instructions

List projects registered via CLI and approved check configurations.

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

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose an important behavioral trait — the result set is scoped to CLI-registered projects and approved check configurations rather than all projects — but says nothing about ordering, permissions, or whether unapproved or UI-created projects are excluded.

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 sentence with no filler, and the core action is front-loaded. The trailing clause is compressed to the point of obscurity, which slightly undercuts the otherwise efficient structure.

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?

For a zero-parameter list tool with no output schema and no annotations, the description is minimally adequate: it identifies the resource and hints at scoping. It leaves the shape of the returned data and the meaning of "approved check configurations" unexplained, which is the main completeness gap.

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 no parameter semantics to explain and the schema coverage is moot. The description correctly makes no parameter claims and does not mislead about inputs.

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?

"List projects" gives a clear verb and resource, and the qualifier "registered via CLI" narrows the scope. However, the second clause "and approved check configurations" is ambiguous — it is unclear whether check configurations are a separate returned entity or an additional filter condition, so an agent cannot fully predict what the response contains.

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 never states when to call this tool, when not to, or how it relates to siblings such as list_runs or get_context. The agent must infer that a zero-parameter project enumeration is the entry point; no routing guidance is provided.

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