Skip to main content
Glama

doer_list_projects

List and search todo list projects and workspaces with counts and pagination to quickly locate relevant Doer projects by name or description.

Instructions

List and search todo list projects and workspaces in Doer with list counts and pagination

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch query to filter projects by name or description
limitNoNumber of projects to return (default 50, max 100)
offsetNoPagination offset (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two useful behavioral traits beyond the schema: results include list counts and are paginated. However, it omits whether this is strictly read-only, any permission requirements, and what the returned records look like.

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 front-loaded sentence with no filler; the core action and the two output traits are stated immediately. Slightly dense but every clause carries information.

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 three-optional-parameter read tool with no output schema and no annotations, the description covers the essentials (search, counts, pagination) but leaves the return shape and read-only nature unstated, which an agent would want before calling.

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%, so all three parameters (q, limit, offset) are already documented with defaults and bounds. The description adds only the general notion of pagination and counts, which the schema largely covers, so baseline 3 applies.

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 pair (list and search) and resource (todo list projects and workspaces), plus the notable output traits (list counts, pagination). It implicitly distinguishes itself from doer_list_todo_lists by naming projects/workspaces, though it never explicitly contrasts the two.

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?

Usage is only implied: the presence of a search query parameter suggests filtering by name/description, but the description never says when to use this versus doer_list_todo_lists or doer_get_project, nor any exclusions or prerequisites.

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