Skip to main content
Glama

List projects

list_projects
Read-onlyIdempotent

The projects that take time, each with its client and tasks: the project tasks whose project_task_id create_time_entry and start_timer need. Call it to find the project and task that the user names. An admin or the owner also gets archived projects with status archived or all, and the rates.

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
statusNoFor an admin and the owner; another role reads the active records that take its time

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is lower, and the description still adds real value: role-dependent visibility (admin/owner additionally see archived projects and the rates) and the cross-tool dependency on project_task_id. It does not mention pagination or result size limits, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler, and the core content is front-loaded. But the first sentence is a tangled chain of relative clauses, and the trailing 'and the rates' is unexplained and reads as an afterthought rather than a deliberate disclosure.

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

Completeness4/5

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

An output schema exists, so return shape need not be spelled out, and the description covers role-based access, the nested task data, and the downstream consumer of project_task_id. For a one-parameter read tool this is close to sufficient; only pagination and result-volume expectations are 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?

Schema coverage is 100% and the single status parameter is already documented in the schema, so the baseline of 3 applies. The description restates the admin/owner-versus-other-role behavior and clarifies that archived/all return archived projects, but adds little that the enum description does not already say.

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?

The description identifies the resource (projects) and what each record carries (its client and the project tasks), plus the task IDs that create_time_entry and start_timer consume. It never uses an explicit verb like 'list' and the phrase 'projects that take time' is idiosyncratic, but an agent can still tell this apart from get_project or list_tasks by the bulk-plus-nested-tasks framing.

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

Usage Guidelines3/5

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

One concrete use case is given: 'Call it to find the project and task that the user names.' That is genuine routing guidance. However, there is no contrast with get_project (single lookup) or list_tasks, and no statement of when not to use this tool, so the agent must infer the boundary from names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources