Skip to main content
Glama
soil-dev

capsulemcp

list_entries

Retrieve a paginated global timeline of all notes, captured emails, and completed tasks across the entire Capsule account, sorted most-recent-first. Ideal for viewing company-wide activity over a period.

Instructions

Global timeline feed: every note, captured email, and completed-task record across the whole Capsule account, paginated. Default order is most-recent-first. Use this for 'what activity happened today/this week across the company?' rather than iterating list_party_entries / list_opportunity_entries / list_project_entries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
perPageNo
embedNoComma-separated embeds, e.g. 'attachments,participants'

Implementation Reference

  • The actual handler function for the 'list_entries' tool. Calls capsuleGet('/entries') with pagination params (page, perPage, embed) and returns the entries data with a nextPage cursor.
    export async function listEntries(input: z.infer<typeof listEntriesSchema>) {
      const { data, nextPage } = await capsuleGet<{ entries: unknown[] }>("/entries", {
        embed: input.embed,
        page: input.page,
        perPage: input.perPage,
      });
      return { ...data, nextPage };
    }
  • Zod schema for 'list_entries' input validation. Uses listEntriesPagination (page with default 1, perPage with default 25, and embed string).
    export const listEntriesSchema = z.object({
      ...listEntriesPagination,
    });
  • Shared pagination fields (page, perPage, embed) used by listEntriesSchema and all list_*_entries schemas.
    const listEntriesPagination = {
      page: z.number().int().positive().optional().default(1),
      perPage: z.number().int().min(1).max(100).optional().default(25),
      embed: z.string().optional().describe(EMBED_ATTACHMENTS_PARTICIPANTS_DESCRIPTION),
    };
  • src/server.ts:690-696 (registration)
    Registration of the 'list_entries' tool via registerTool helper. Maps the tool name 'list_entries' to listEntriesSchema and listEntries handler.
    registerTool(
      server,
      "list_entries",
      "Global timeline feed: every note, captured email, and completed-task record across the whole Capsule account, paginated. Default order is most-recent-first. Use this for 'what activity happened today/this week across the company?' rather than iterating list_party_entries / list_opportunity_entries / list_project_entries.",
      listEntriesSchema,
      listEntries,
    );
  • Generic registerTool helper that wraps a handler's return value in the MCP text-content response shape and registers it with the MCP SDK server.
    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);
      });
    }
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It mentions pagination and default ordering (most-recent-first), which are useful. However, it does not disclose other behaviors such as permission requirements, rate limits, behavior on empty results, or the structure of the response. Given no annotations, the additional context is adequate but not exhaustive.

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?

The description is two sentences long, efficiently conveying purpose, scope, usage guidance, and parameter implications. It is appropriately sized and front-loaded with the most important information.

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?

The description covers the main use case, pagination, and comparison with sibling tools. However, without an output schema, it does not describe the return fields, and it could mention edge cases or additional behavior. For a list tool with no annotations, it is fairly complete but misses some contextual details.

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?

The input schema has 3 parameters: page, perPage, and embed. The description adds value by clarifying pagination, but does not explicitly describe the parameters or the embed option. With schema description coverage at 33% (only embed has a description), the description does not fully compensate for the missing documentation. The baseline is 3 due to low coverage, and the description provides minimal additional meaning.

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?

The description specifies the tool as a global timeline feed covering notes, captured emails, and completed-task records across the entire Capsule account. It clearly distinguishes from sibling tools by naming list_party_entries, list_opportunity_entries, and list_project_entries as alternatives that should not be used for this purpose.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool: for asking 'what activity happened today/this week across the company?' and when not: instead of iterating over specific sibling tools. This provides clear context and 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