Skip to main content
Glama

board_list_charters

Read-onlyIdempotent

List all charters under a governed institution to obtain charter IDs, types, deliberation modes, seat configurations, and status for convening sessions.

Instructions

List all charters (boards, committees, subcommittees) under a governed institution. Returns charter IDs, types, deliberation modes, seat configurations, and status. Use charter_id to convene sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
institution_idYesInstitution ID from board_list_institutions

Implementation Reference

  • The handler/implementation of the board_list_charters tool. It registers the tool on the McpServer with a required institution_id (string) Zod schema. The handler calls GET /api/institution/{institution_id}/charters, maps the response to include charter details (id, name, type, status, deliberation mode, seats, decision rights), and returns a formatted JSON response.
    // board_list_charters — list charters under an institution
    // =========================================================================
    server.tool(
      'board_list_charters',
      'List all charters (boards, committees, subcommittees) under a governed institution. Returns charter IDs, types, deliberation modes, seat configurations, and status. Use charter_id to convene sessions.',
      {
        institution_id: z.string().describe('Institution ID from board_list_institutions'),
      },
      { title: 'List Charters', readOnlyHint: true, idempotentHint: true, destructiveHint: false, openWorldHint: false },
      async (args) => {
        try {
          const data = await apiCall(`/api/institution/${args.institution_id}/charters`, 'GET') as any;
          const charters = (data.charters || data || []) as any[];
    
          return {
            content: [{ type: 'text' as const, text: JSON.stringify({
              institution_id: args.institution_id,
              count: charters.length,
              charters: charters.map((c: any) => ({
                charter_id:    c.charter_id,
                name:          c.name,
                short_code:    c.short_code,
                type:          c.type,
                status:        c.status,
                parent_id:     c.parent_id,
                deliberation_mode: c.charter_document?.deliberation?.mode,
                seat_count:    c.charter_document?.membership?.seats?.length,
                seats:         c.charter_document?.membership?.seats?.map((s: any) => ({
                  role: s.role, label: s.label, model: s.model,
                })),
                decision_rights: {
                  mandatory:    c.charter_document?.decisionRights?.mandatory,
                  advisory:     c.charter_document?.decisionRights?.advisory,
                  prohibited:   c.charter_document?.decisionRights?.prohibited,
                },
                cadence: c.cadence,
                compliance_frameworks: c.compliance_frameworks,
              })),
              next_step: `Call board_convene_session with institution_id and charter_id to start a governed deliberation`,
            }, null, 2) }],
          };
        } catch (err: unknown) {
          return boardErrorResponse(err);
        }
      }
    );
  • Zod input schema for board_list_charters: requires institution_id as a string (from board_list_institutions).
    {
      institution_id: z.string().describe('Institution ID from board_list_institutions'),
    },
  • The export function registerInstitutionTools that registers all board tools including board_list_charters on the MCP server.
    export function registerInstitutionTools(server: McpServer): void {
  • Import of registerInstitutionTools from the institution.ts module.
    import { registerInstitutionTools } from './tools/institution.js';
  • Registration of board tools (including board_list_charters) in the TOOL_REGISTRY under the 'tenant' visibility tier.
    { tier: 'tenant', register: (server, _engine) => registerInstitutionTools(server), description: 'board (list_institutions, list_charters, convene_session, get_session, install_kit)' },
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description aligns. It adds behavioral details beyond annotations by specifying the return fields (charter IDs, types, deliberation modes, etc.), which helps the agent understand what to expect. No contradictions.

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: the first states the core action and scope, the second lists return fields and a usage hint. Every sentence adds value, and the most critical information is front-loaded.

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

Completeness5/5

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

Given no output schema, the description adequately covers what the tool returns (charter IDs, types, deliberation modes, seat configurations, status) and provides a useful hint for the next step (convening sessions). This is complete for a list operation.

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% (institution_id described as 'from board_list_institutions'). The description does not add additional semantic information about the parameter beyond what the schema provides, so a baseline score of 3 is appropriate.

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 all charters under a governed institution, explicitly naming the resource (charters) and elaborating with examples (boards, committees, subcommittees). It distinguishes from sibling tools like board_list_institutions by focusing on charters, not institutions.

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?

The description provides clear context (list charters for a given institution) and hints at downstream usage ('Use charter_id to convene sessions'), but does not explicitly state when not to use this tool or contrast with alternatives like board_search_precedent.

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/knowledgepa3/gia-mcp-server'

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