Skip to main content
Glama
RRGU26

BankRegPulse

get_daily_briefing

Retrieve daily banking regulatory intelligence briefings with summaries and key developments from federal agencies and state banking departments.

Instructions

Get the latest daily banking regulatory intelligence briefing with summaries and key developments from OCC, FDIC, CFPB, Federal Reserve, and all 50 state banking departments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoOptional: Specific date (YYYY-MM-DD). Defaults to today.

Implementation Reference

  • The getDailyBriefing function implements the core tool logic. It constructs the API URL with an optional date parameter, fetches data from the BankRegPulse API, handles error responses, and formats the briefing data into a structured text response with subject, date, document count, priority count, and AI summary.
    async function getDailyBriefing(date?: string) {
      const url = date
        ? `${API_BASE_URL}/api/mcp/briefing?date=${date}`
        : `${API_BASE_URL}/api/mcp/briefing`;
    
      const response = await fetch(url);
    
      if (!response.ok) {
        throw new Error(`API request failed: ${response.statusText}`);
      }
    
      const data = await response.json() as any;
    
      if (!data.success || !data.data) {
        return {
          content: [
            {
              type: 'text',
              text: 'No briefing found for the requested date.',
            },
          ],
        };
      }
    
      const briefing = data.data;
      const dateStr = new Date(briefing.sentAt).toLocaleDateString();
    
      return {
        content: [
          {
            type: 'text',
            text: `# ${briefing.subject}\n\n**Date:** ${dateStr}\n**Documents:** ${briefing.totalDocuments}\n**High Priority:** ${briefing.highPriorityCount}\n\n${briefing.aiSummary}\n\n---\n*Powered by BankRegPulse*`,
          },
        ],
      };
    }
  • Tool schema definition for get_daily_briefing in the TOOLS array, including name, description, and inputSchema with an optional date property (YYYY-MM-DD format) that defaults to today.
    const TOOLS: Tool[] = [
      {
        name: 'get_daily_briefing',
        description: 'Get the latest daily banking regulatory intelligence briefing with summaries and key developments from OCC, FDIC, CFPB, Federal Reserve, and all 50 state banking departments.',
        inputSchema: {
          type: 'object',
          properties: {
            date: {
              type: 'string',
              description: 'Optional: Specific date (YYYY-MM-DD). Defaults to today.',
            },
          },
        },
      },
  • src/index.ts:102-103 (registration)
    The switch case in the CallToolRequestSchema handler that routes get_daily_briefing tool invocations to the getDailyBriefing function, passing through the date argument.
    case 'get_daily_briefing':
      return await getDailyBriefing(toolArgs.date as string | undefined);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes what the tool retrieves (briefing with summaries and key developments) but lacks critical behavioral details such as whether this is a read-only operation, if it requires authentication, rate limits, data freshness, or error handling. The description is functional but misses key operational context.

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

Conciseness4/5

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

The description is a single, well-structured sentence that efficiently conveys the tool's purpose and scope without unnecessary words. It front-loads the key action ('Get the latest daily banking regulatory intelligence briefing') and follows with specific details. While concise, it could be slightly improved by breaking into two sentences for readability, but overall it earns its place with zero waste.

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?

Given the tool's moderate complexity (retrieving structured regulatory data), lack of annotations, and no output schema, the description is minimally complete. It specifies content sources and type but omits details on output format, data structure, or error conditions. The description provides enough to understand the tool's intent but leaves gaps in practical usage context that the agent must infer or discover through trial.

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 'date' well-documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as date format examples or default behavior details. However, with high schema coverage and only one optional parameter, the baseline score of 3 is appropriate as the schema adequately handles parameter semantics.

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's purpose with a specific verb ('Get') and resource ('daily banking regulatory intelligence briefing'), and distinguishes it from sibling tools by specifying the content type (briefing vs. podcast or LinkedIn post). It explicitly lists the sources covered (OCC, FDIC, CFPB, Federal Reserve, all 50 state banking departments), making the scope unambiguous.

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

Usage Guidelines3/5

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

The description implies usage context by specifying the content type and sources, but does not explicitly state when to use this tool versus alternatives like get_daily_podcast or get_linkedin_post. It provides no guidance on prerequisites, exclusions, or comparative scenarios, leaving the agent to infer usage based on content differences alone.

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/RRGU26/bank-reg-pulse'

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