Skip to main content
Glama
soil-dev

capsulemcp

list_boards

Get a list of all project boards with their IDs, names, and stages to use as boardId when creating a new project.

Instructions

List all project (case) boards defined in Capsule. A board is a grouping of stages that projects flow through — the project equivalent of an opportunity pipeline. Returns each board's id, name, and stages. Use this to discover boardId when creating a project, then pick a starting stage via list_stages. Like pipelines, boards are stable per account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
perPageNo

Implementation Reference

  • The listBoards function: the actual handler that calls capsuleGet('/boards') to fetch paginated board data and returns it with a nextPage cursor.
    export async function listBoards(input: z.infer<typeof listBoardsSchema>) {
      const { data, nextPage } = await capsuleGet<{ boards: unknown[] }>("/boards", {
        page: input.page ?? 1,
        perPage: input.perPage ?? 100,
      });
      return { ...data, nextPage };
    }
  • listBoardsSchema: Zod schema defining the input — optional page and perPage pagination fields.
    export const listBoardsSchema = z.object({ ...paginationFields });
  • src/server.ts:860-866 (registration)
    Tool registration for 'list_boards' in src/server.ts, calling registerTool with name, description, schema, and handler.
    registerTool(
      server,
      "list_boards",
      "List all project (case) boards defined in Capsule. A board is a grouping of stages that projects flow through — the project equivalent of an opportunity pipeline. Returns each board's id, name, and stages. Use this to discover boardId when creating a project, then pick a starting stage via list_stages. Like pipelines, boards are stable per account.",
      listBoardsSchema,
      listBoards,
    );
  • registerTool helper function that wraps handler return values in MCP's text content response format.
    export function registerTool<Schema extends z.ZodObject<ZodRawShape>>(
      server: McpServer,
      name: string,
      description: string,
      schema: Schema,
      handler: (input: z.infer<Schema>) => Promise<unknown>,
    ): void {
      // Use the SDK config-form registerTool with the full Zod schema. The
      // deprecated shape overload rebuilds z.object(schema.shape), which drops
      // object-level refinements such as superRefine.
      const registerWithSchema = server.registerTool.bind(server) as (
        toolName: string,
        config: { description: string; inputSchema: Schema },
        callback: (input: z.infer<Schema>) => Promise<CallToolResult>,
      ) => void;
    
      registerWithSchema(name, { description, inputSchema: schema }, async (input) => {
        const result = await handler(input);
        return wrapAsText(result);
      });
    }
  • capsuleGet: the generic HTTP GET helper used by listBoards to call the Capsule CRM API with pagination.
    export async function capsuleGet<T>(path: string, params?: QueryParams): Promise<PagedResult<T>> {
      const token = getToken();
      const url = buildUrl(path, params);
      const { res, cleanup } = await doFetch(url, { headers: baseHeaders(token) });
      try {
        const data = await handleResponse<T>(res);
        const nextPage = parseNextPage(res.headers.get("Link"));
        return { data, nextPage };
      } finally {
        cleanup();
      }
    }
Behavior3/5

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

No annotations provided, so description carries full burden. Indicates it returns data (id, name, stages) but does not explicitly state it is read-only, non-destructive, or mention authentication or rate limits. Adequate for a simple list operation.

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

Conciseness5/5

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

Four sentences, no wasted words. Front-loaded with purpose and essential context. Each sentence adds value.

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?

Covers purpose, return values, and usage context. However, lacks explanation of pagination parameters (page, perPage) and default behavior, which is important for a list tool that may return many results.

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

Parameters1/5

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

Input schema has 2 parameters (page, perPage) with 0% schema description coverage. The description does not explain these parameters at all, leaving the agent with no semantic guidance beyond raw constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool lists all project boards, explains what a board is (grouping of stages), and specifies the return fields (id, name, stages). Distinguishes from siblings like list_pipelines and list_stages.

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

Usage Guidelines4/5

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

Provides explicit usage guidance: use to discover boardId when creating a project, then select a starting stage via list_stages. Notes that boards are stable per account. Does not include explicit exclusions or comparisons to alternatives.

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/soil-dev/capsulemcp'

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