Skip to main content
Glama

List to-do lists for a project

list_todolists

Retrieve and display to-do lists from a Basecamp project by providing the project ID to manage tasks and organize work.

Instructions

Resolves the project's to-do set from dock, then lists its to-do lists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Implementation Reference

  • Executes the list_todolists tool: resolves todoset from project dock, fetches todolists via API, formats as numbered list.
    async ({ project_id }) => {
      const resolved = await getTodosetFromDock(project_id);
      if (!resolved) {
        return {
          content: [
            { type: "text", text: "No to-do set found in the project's dock." },
          ],
        };
      }
      const lists = await bcRequest<any[]>(
        "GET",
        `/buckets/${project_id}/todosets/${resolved.id}/todolists.json`
      );
      const text =
        Array.isArray(lists) && lists.length
          ? lists.map((t: any) => `${t.id}: ${t.name}`).join("\n")
          : "No to-do lists found.";
      return {
        content: [{ type: "text", text: `To-do set ${resolved.id}\n${text}` }],
      };
    }
  • Input schema, title, and description for the list_todolists tool.
    {
      title: "List to-do lists for a project",
      description:
        "Resolves the project's to-do set from dock, then lists its to-do lists.",
      inputSchema: { project_id: z.number().int() },
    },
  • Direct registration of the list_todolists tool within registerTodosetTools function.
    server.registerTool(
      "list_todolists",
      {
        title: "List to-do lists for a project",
        description:
          "Resolves the project's to-do set from dock, then lists its to-do lists.",
        inputSchema: { project_id: z.number().int() },
      },
      async ({ project_id }) => {
        const resolved = await getTodosetFromDock(project_id);
        if (!resolved) {
          return {
            content: [
              { type: "text", text: "No to-do set found in the project's dock." },
            ],
          };
        }
        const lists = await bcRequest<any[]>(
          "GET",
          `/buckets/${project_id}/todosets/${resolved.id}/todolists.json`
        );
        const text =
          Array.isArray(lists) && lists.length
            ? lists.map((t: any) => `${t.id}: ${t.name}`).join("\n")
            : "No to-do lists found.";
        return {
          content: [{ type: "text", text: `To-do set ${resolved.id}\n${text}` }],
        };
      }
    );
  • Helper to resolve todoset ID and URL from a project's Basecamp dock, used by list_todolists.
    async function getTodosetFromDock(
      project_id: number
    ): Promise<{ id: number; url: string } | null> {
      const project = await bcRequest<any>("GET", `/projects/${project_id}.json`);
      const dock = Array.isArray(project?.dock) ? project.dock : [];
      const todoset = dock.find((d: any) => (d?.name || d?.app_name) === "todoset");
      if (!todoset) return null;
      const href: string =
        todoset.url || todoset.href || todoset.api_url || todoset.app_url || "";
      const m = href.match(/\/todosets\/(\d+)/);
      return m ? { id: Number(m[1]), url: href } : null;
    }
  • Top-level registration call that invokes the function registering list_todolists.
    registerTodosetTools(server);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'resolves the project's to-do set from dock', which hints at some internal process but doesn't clarify if this is a read-only operation, what permissions are needed, or how errors are handled. The description lacks details on output format, pagination, or rate limits, leaving significant gaps for a tool with no annotation coverage.

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?

The description is brief with two sentences, but the first sentence ('Resolves the project's to-do set from dock') is unclear and doesn't contribute meaningfully to understanding the tool's purpose. The second sentence is more direct but could be more front-loaded. Overall, it's concise but includes wasted phrasing that reduces clarity.

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

Completeness2/5

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

Given no annotations, no output schema, and low schema description coverage (0%), the description is incomplete. It fails to explain parameters, behavioral traits, or return values, making it inadequate for an agent to use the tool effectively. The vague phrasing adds confusion rather than compensating for the lack of structured data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, so the description must compensate. It does not mention the 'project_id' parameter at all, failing to explain what it represents, how to obtain it, or its format. This leaves the parameter undocumented beyond the schema's basic type, adding no semantic value.

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?

The description states the tool 'lists to-do lists for a project', which clarifies the verb (list) and resource (to-do lists) with a scope (for a project). However, it includes vague phrasing like 'resolves the project's to-do set from dock', which adds confusion without clear meaning, and it doesn't explicitly differentiate from sibling tools like 'list_projects' or 'get_todoset'.

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 implies usage by mentioning 'for a project', but provides no explicit guidance on when to use this tool versus alternatives like 'list_projects' or 'get_todoset'. There are no exclusions, prerequisites, or comparisons to sibling tools, leaving the agent with minimal context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/craigashields/basecamp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server