Skip to main content
Glama
RRGU26

BankRegPulse

get_daily_podcast

Retrieve daily regulatory podcast audio with AI-generated summaries of banking developments from OCC, FDIC, CFPB, Federal Reserve, and state agencies.

Instructions

Get the latest daily regulatory podcast audio URL. Listen to an AI-generated summary of the day's regulatory developments.

Input Schema

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

Implementation Reference

  • The main handler function getDailyPodcast that implements the tool logic. It constructs the API URL (with optional date parameter), fetches podcast data from the API, handles errors and missing data, constructs the audio URL, and returns a formatted text response with the podcast information including date and audio URL.
    async function getDailyPodcast(date?: string) {
      const url = date
        ? `${API_BASE_URL}/api/mcp/podcast?date=${date}`
        : `${API_BASE_URL}/api/mcp/podcast`;
    
      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 podcast found for the requested date.',
            },
          ],
        };
      }
    
      const podcast = data.data;
      const dateStr = new Date(podcast.sentAt).toLocaleDateString();
      const audioUrl = `${API_BASE_URL}/api/podcast/${podcast.id}/audio`;
    
      return {
        content: [
          {
            type: 'text',
            text: `# Daily Regulatory Podcast\n\n**Date:** ${dateStr}\n**Audio URL:** ${audioUrl}\n\nCopy the URL above to listen to today's regulatory briefing.\n\n---\n*Powered by BankRegPulse*`,
          },
        ],
      };
    }
  • src/index.ts:62-74 (registration)
    Tool registration/definition in the TOOLS array. Defines the tool name 'get_daily_podcast', its description for users, and the inputSchema specifying an optional 'date' parameter in YYYY-MM-DD format.
    {
      name: 'get_daily_podcast',
      description: 'Get the latest daily regulatory podcast audio URL. Listen to an AI-generated summary of the day\'s regulatory developments.',
      inputSchema: {
        type: 'object',
        properties: {
          date: {
            type: 'string',
            description: 'Optional: Specific date (YYYY-MM-DD). Defaults to today.',
          },
        },
      },
    },
  • src/index.ts:105-106 (registration)
    The switch case handler that routes tool calls to the getDailyPodcast function when the tool name is 'get_daily_podcast'. It extracts the optional date parameter from the tool arguments and passes it to the handler.
    case 'get_daily_podcast':
      return await getDailyPodcast(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 mentions retrieving a 'URL' and an 'AI-generated summary,' but doesn't disclose critical traits like whether this is a read-only operation, if it requires authentication, rate limits, error handling, or what format the output takes. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 concise and front-loaded, with two sentences that directly state the tool's function. There's no unnecessary information, and each sentence contributes to understanding the purpose. However, it could be slightly more structured by separating the URL retrieval and summary aspects more clearly.

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

Completeness2/5

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

Given the complexity of retrieving media content with no annotations and no output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., URL format, summary text), error cases, or behavioral details. For a tool that likely involves network calls and content delivery, more context is needed to use it effectively.

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 one optional parameter 'date' clearly documented. The description doesn't add any parameter-specific semantics beyond what the schema provides (e.g., it doesn't explain date format constraints or default behavior further). With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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: 'Get the latest daily regulatory podcast audio URL' and 'Listen to an AI-generated summary of the day's regulatory developments.' It specifies the verb ('Get'), resource ('podcast audio URL'), and content type ('regulatory podcast'). However, it doesn't explicitly distinguish this from sibling tools like 'get_daily_briefing' or 'get_linkedin_post' beyond mentioning 'podcast' vs 'briefing'/'post'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools, prerequisites, or exclusions. The only implied context is for accessing daily regulatory content, but this is vague and doesn't help an agent choose between this and other tools like 'get_daily_briefing'.

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