Skip to main content
Glama
r-huijts

OpenTK Model Context Protocol Server

by r-huijts

birthdays_today

Retrieve a list of Dutch Members of Parliament celebrating their birthdays today, including names, political parties, and birth dates. Use for 'on this day' content or specific birthday inquiries. Returns JSON data for easy integration.

Instructions

Lists all Members of Parliament celebrating their birthday today, including their names, political parties, and birth dates. The response is a JSON array where each entry contains the MP's ID, name, party affiliation, and other details. Use this tool when a user specifically asks about birthdays, wants to know which MPs are celebrating today, or needs to create 'on this day' content. This tool takes no parameters as it always returns today's birthdays. For a more general overview that includes birthdays along with other parliamentary information, use the 'get_overview' tool instead. If you need to display an MP's photo alongside their birthday information, you can use the 'get_photo' tool with the MP's ID from this response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The complete registration, schema (empty input), and inline handler for the 'birthdays_today' MCP tool. The handler fetches JSON data from the '/jarig-vandaag' API endpoint using apiService and returns it as a formatted text content block, with error handling.
      "birthdays_today",
      "Lists all Members of Parliament celebrating their birthday today, including their names, political parties, and birth dates. The response is a JSON array where each entry contains the MP's ID, name, party affiliation, and other details. This tool takes no parameters as it always returns today's birthdays. Applicable when information about MPs' birthdays is needed.",
      {},
      async () => {
        try {
          const data = await apiService.fetchJson(`/jarig-vandaag`);
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error: any) {
          return {
            content: [{
              type: "text",
              text: `Error fetching birthdays: ${error.message || 'Unknown error'}`
            }]
          };
        }
      }
    );
  • The generic fetchJson helper method in ApiService used by the birthdays_today handler to retrieve JSON data from the tkconv API endpoint '/jarig-vandaag'.
    async fetchJson<T>(path: string, options: RequestInit = {}): Promise<T> {
      try {
        // Ensure the path starts with a slash
        const normalizedPath = path.startsWith('/') ? path : `/${path}`;
    
        // Set default headers if not provided
        const headers = {
          'User-Agent': 'Mozilla/5.0 (compatible; OpenTK-MCP/1.0)',
          ...options.headers
        };
    
        const res = await fetch(`${BASE_URL}${normalizedPath}`, {
          ...options,
          headers,
          agent: ApiService.agent
        } as NodeRequestInit);
    
        if (!res.ok) {
          throw new Error(`API error: ${res.status} ${res.statusText}`);
        }
    
        const text = await res.text();
    
        // Check if the response is HTML
        if (text.trim().startsWith('<!DOCTYPE')) {
          return {} as T;
        }
    
        // Parse JSON
        try {
          return JSON.parse(text) as T;
        } catch (error) {
          return {} as T;
        }
      } catch (error) {
        throw error;
      }
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly describes the tool's behavior: it returns today's birthdays only (not historical or future dates), outputs a JSON array with specific fields (ID, name, party, etc.), and has no parameters. However, it doesn't mention potential limitations like rate limits, authentication needs, or error conditions.

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 well-structured and front-loaded with the core purpose, followed by usage guidelines and alternatives. Every sentence adds value: the first explains what the tool does, the second describes the output format, the third provides usage scenarios, the fourth explains the lack of parameters, and the last two offer sibling tool alternatives.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is largely complete. It covers purpose, output format, usage guidelines, and alternatives. However, without annotations or output schema, it could benefit from more detail on behavioral aspects like error handling or data freshness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so the baseline is 4. The description adds value by explicitly stating 'This tool takes no parameters as it always returns today's birthdays,' which clarifies why there are no parameters and reinforces the tool's fixed scope.

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 specific action ('Lists all Members of Parliament celebrating their birthday today') and the resource ('Members of Parliament'), distinguishing it from siblings like 'get_overview' or 'list_persons' by focusing exclusively on today's birthdays. It provides concrete details about what information is included (names, political parties, birth dates).

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 explicitly states when to use this tool ('when a user specifically asks about birthdays, wants to know which MPs are celebrating today, or needs to create 'on this day' content') and provides clear alternatives ('use the 'get_overview' tool instead' for general overview, and 'use the 'get_photo' tool' for photos). It effectively guides the agent on tool selection.

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

Related 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/r-huijts/opentk-mcp'

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