Skip to main content
Glama

tb_list_boards

Retrieve all task boards with optional project filtering to obtain board IDs for subsequent operations.

Instructions

List all task boards, optionally filtered by project. Use this to discover board IDs after context loss.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNoFilter by project

Implementation Reference

  • The tool handler for 'tb_list_boards'. It calls getDb(), optionally filters boards by project using a SQL query, and returns all boards ordered by created_at DESC.
    server.tool(
      "tb_list_boards",
      "List all task boards, optionally filtered by project. Use this to discover board IDs after context loss.",
      {
        project: z.string().optional().describe("Filter by project"),
      },
      async ({ project }) => {
        const db = getDb();
        const boards = project
          ? db.prepare(`SELECT * FROM boards WHERE project = ? ORDER BY created_at DESC`).all(project)
          : db.prepare(`SELECT * FROM boards ORDER BY created_at DESC`).all();
    
        return {
          content: [{ type: "text" as const, text: JSON.stringify({ boards }) }],
        };
      }
    );
  • Input schema for tb_list_boards: accepts an optional 'project' string filter.
    {
      project: z.string().optional().describe("Filter by project"),
    },
  • Registration call: server.tool('tb_list_boards', ...) inside registerTaskBoardTools().
    "tb_list_boards",
  • src/server.ts:19-19 (registration)
    Registration is invoked via registerTaskBoardTools(server) in the createServer() function.
    registerTaskBoardTools(server);
  • getDb() helper that initializes and returns the SQLite database instance used by the handler.
    export function getDb(): Database.Database {
      if (db) return db;
    
      fs.mkdirSync(path.dirname(DB_PATH), { recursive: true });
    
      db = new Database(DB_PATH);
      db.pragma("journal_mode = WAL");
      db.pragma("synchronous = normal");
      db.pragma("cache_size = -32000");
      db.pragma("temp_store = memory");
      db.pragma("busy_timeout = 5000");
      db.pragma("foreign_keys = ON");
    
      const versionInfo = db.prepare("SELECT sqlite_version() as version").get() as { version: string };
      console.error(`ForgeSpec MCP: SQLite ${versionInfo.version}, WAL mode enabled`);
    
      initSchema(db);
      return db;
    }
Behavior3/5

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

With no annotations, the description carries the full burden. It correctly implies a read-only listing operation via the verb 'List'. But it does not disclose any additional behavioral traits such as permissions, rate limits, or the scope of data returned.

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?

Two concise sentences: the first states the action, the second provides a practical use case. No redundant 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 simple list tool with no output schema, the description adequately states its purpose and when to use it. However, it omits details about the return format or fields, which might be necessary for an agent to fully utilize the tool.

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 coverage is 100% (one parameter fully described). The description repeats the schema's 'Filter by project' without adding new meaning, so it meets the baseline but does not exceed it.

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 clearly states the tool lists task boards with optional filtering by project, and explicitly says to use it for discovering board IDs after context loss. This differentiates it from siblings like tb_get and tb_create_board.

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 specific context for use ('after context loss'), implying a slot for discovering board IDs. However, it does not explicitly exclude cases where other tools (e.g., tb_get) would be more appropriate, nor does it enumerate 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/lleontor705/forgespec-mcp'

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