Skip to main content
Glama

councly_status

Check council hearing status to get current phase, progress, verdict, trust scores, and counsel summaries for AI-debated topics.

Instructions

Check the status of a council hearing.

Returns:

  • For in-progress hearings: current phase and progress percentage

  • For completed hearings: verdict, trust score, and counsel summaries

  • For failed hearings: error message

Use this to check on hearings created with wait=false, or to retrieve past hearing results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hearing_idYesThe hearing ID to check

Implementation Reference

  • Handler for the councly_status tool: parses the input using counclyStatusSchema, fetches the hearing status via CounclyClient.getHearingStatus(hearing_id), formats the result with formatHearingResult, and returns it as MCP text content.
    case 'councly_status': {
      const parsed = counclyStatusSchema.parse(args);
      const status = await client.getHearingStatus(parsed.hearing_id);
    
      return {
        content: [
          {
            type: 'text',
            text: formatHearingResult(status),
          },
        ],
      };
    }
  • Zod schema definition for councly_status tool input validation, requiring a UUID hearing_id. Includes TypeScript type inference.
    export const counclyStatusSchema = z.object({
      hearing_id: z.string().uuid().describe('The hearing ID returned from councly_hearing'),
    });
    
    export type CounclyHearingInput = z.infer<typeof counclyHearingSchema>;
    export type CounclyStatusInput = z.infer<typeof counclyStatusSchema>;
  • src/tools.ts:91-112 (registration)
    MCP tool registration/definition for councly_status, including name, description, and inputSchema used in listTools response.
      {
        name: 'councly_status',
        description: `Check the status of a council hearing.
    
    Returns:
    - For in-progress hearings: current phase and progress percentage
    - For completed hearings: verdict, trust score, and counsel summaries
    - For failed hearings: error message
    
    Use this to check on hearings created with wait=false, or to retrieve past hearing results.`,
        inputSchema: {
          type: 'object',
          properties: {
            hearing_id: {
              type: 'string',
              format: 'uuid',
              description: 'The hearing ID to check',
            },
          },
          required: ['hearing_id'],
        },
      },
  • Helper function to format hearing status into a readable Markdown string, used by both councly_hearing (when waiting) and councly_status tools.
    // Format hearing result for display
    function formatHearingResult(status: {
      hearingId: string;
      status: string;
      verdict?: string | null;
      trustScore?: number | null;
      totalCost?: number;
      counselSummaries?: Array<{
        seat: string;
        model: string;
        lastTurn: string;
      }>;
      progress?: number;
      error?: string;
    }): string {
      const lines: string[] = [];
    
      lines.push(`## Hearing ${status.hearingId}`);
      lines.push(`**Status:** ${status.status}`);
    
      if (status.status === 'completed' || status.status === 'early_stopped') {
        if (status.verdict) {
          lines.push('');
          lines.push('### Verdict');
          lines.push(status.verdict);
        }
    
        if (status.trustScore !== null && status.trustScore !== undefined) {
          lines.push('');
          lines.push(`**Trust Score:** ${status.trustScore}/100`);
        }
    
        if (status.counselSummaries && status.counselSummaries.length > 0) {
          lines.push('');
          lines.push('### Counsel Perspectives');
          for (const counsel of status.counselSummaries) {
            lines.push(`**${counsel.seat}** (${counsel.model}):`);
            lines.push(counsel.lastTurn);
            lines.push('');
          }
        }
    
        if (status.totalCost !== undefined) {
          lines.push(`**Cost:** ${status.totalCost} credits`);
        }
      } else if (status.status === 'failed') {
        lines.push(`**Error:** ${status.error || 'Unknown error'}`);
      } else {
        // In progress
        if (status.progress !== undefined) {
          lines.push(`**Progress:** ${status.progress}%`);
        }
      }
    
      return lines.join('\n');
    }
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the tool's behavior by describing different return scenarios (in-progress, completed, failed) and what information each provides. However, it doesn't mention error handling beyond 'error message', rate limits, authentication requirements, or whether this is a read-only 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?

The description is efficiently structured with three distinct parts: purpose statement, return value scenarios, and usage guidelines. Every sentence adds value, with no redundant or unnecessary information. It's appropriately sized for the tool's complexity.

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?

For a single-parameter status-checking tool with no output schema, the description provides good context: purpose, return scenarios, and usage guidelines. It could be more complete by explicitly stating this is a read-only operation and providing more detail about error conditions, but it covers the essential information an agent needs to use the tool correctly.

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 100% description coverage, with the single parameter 'hearing_id' well-documented as a UUID. The description doesn't add any parameter-specific information beyond what the schema provides, so the baseline score of 3 is appropriate given the schema does all the work.

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

Purpose4/5

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

The description clearly states the tool's purpose as 'Check the status of a council hearing' with specific verb+resource. It distinguishes from the sibling tool 'councly_hearing' by focusing on status checking rather than hearing creation/management, though it doesn't explicitly contrast them.

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 provides explicit usage guidance: 'Use this to check on hearings created with wait=false, or to retrieve past hearing results.' This clearly indicates when to use this tool versus alternatives, including specific scenarios and timing considerations.

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/slmnsrf/councly-mcp'

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