Skip to main content
Glama

List projects

list_projects
Read-onlyIdempotent

List accessible projects in the connected workspace. Use returned IDs for later actions. Keep ordering unchanged across cursor pages.

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
afterNoPagination cursor from the previous nextCursor. Keep filters and ordering unchanged; omit for the first page.
limitNoMaximum number of items to return, from 1 to 100. Defaults to 50.
orderNoResult ordering. Defaults to most recently updated first. Keep the same order while paging.UPDATED_DESC

Output Schema

NameRequiredDescriptionDefault
itemsYesAccessible records on this page.
nextCursorYesPass as after for the next page; null when this page has no continuation cursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds the useful access-scoping fact ('accessible projects') and a paging-stability warning, but that warning largely restates the schema's own 'Keep the same order while paging' note, and nothing is said about result volume or cursor lifetime.

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, front-loaded with what the tool returns and followed by the two operational caveats. The paging-stability sentence is partially redundant with the schema, which costs it a point, but there is no filler.

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 explained, and the input schema is fully self-documenting. For a simple read-only three-parameter list tool the description covers purpose, downstream use, and paging discipline; only the absence of any alternative-routing guidance keeps it from 5.

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 description coverage is 100%, with limit bounds, the order enum, and the cursor format all documented inline, so baseline is 3. The description's mention of ordering across cursor pages overlaps the 'after' and 'order' parameter descriptions instead of adding new meaning.

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 and resource ('List accessible projects') plus scope ('in the connected workspace'), which cleanly separates it from siblings like list_tasks, list_files, and list_conversations. It stops short of naming a sibling or contrasting with a filtered alternative, so it is clear but not maximally differentiated.

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?

'Use returned IDs for later actions' gives downstream-usage guidance and implicitly frames this as the discovery step before get_task/create_task-style calls. There is no explicit when-not-to-use or alternative named, so the guidance remains implied rather than directive.

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.