Skip to main content
Glama
pace8

mcp-hypotheken-berekenen

haal_actuele_rentes_op

Retrieve current mortgage interest rates for different fixed-rate periods, including NHG and non-NHG rates, to support mortgage planning decisions.

Instructions

Haalt actuele hypotheekrentes op per rentevaste periode. Output: overzicht met NHG- en niet-NHG-tarieven.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'haal_actuele_rentes_op' tool. Extracts optional session ID, enforces rate limiting if present, performs a GET request to the configured Replit API URL for current rates using ApiClient, and returns the JSON-formatted response.
    async function handleActueleRentes(request: any): Promise<ToolResponse> {
      const sessionId = extractSessionId(request.params?.arguments);
      if (sessionId) {
        enforceRateLimit(sessionId);
      }
    
      const apiClient = getApiClient();
      const { data } = await apiClient.get(REPLIT_API_URL_RENTES, { correlationId: sessionId });
      return successResponse(JSON.stringify(data, null, 2));
    }
  • src/index.ts:766-774 (registration)
    Registration of all tool handlers in the TOOL_HANDLERS map, including 'haal_actuele_rentes_op' mapped to handleActueleRentes.
    const TOOL_HANDLERS: Record<string, ToolHandler> = {
      bereken_hypotheek_starter: handleBerekenStarter,
      bereken_hypotheek_doorstromer: handleBerekenDoorstromer,
      bereken_hypotheek_uitgebreid: handleBerekenUitgebreid,
      haal_actuele_rentes_op: handleActueleRentes,
      opzet_hypotheek_starter: handleOpzetStarter,
      opzet_hypotheek_doorstromer: handleOpzetDoorstromer,
      opzet_hypotheek_uitgebreid: handleOpzetUitgebreid,
    };
  • src/index.ts:870-877 (registration)
    Tool registration and schema definition returned by ListToolsRequestHandler. Defines the tool name, description, and empty input schema (no parameters required).
      name: "haal_actuele_rentes_op",
      description: "Haalt actuele hypotheekrentes op per rentevaste periode. Output: overzicht met NHG- en niet-NHG-tarieven.",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Input schema for the tool: an empty object (no required parameters).
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Configuration constant for the Replit API endpoint URL used to fetch current interest rates.
    const REPLIT_API_URL_RENTES = config.replitApiUrlRentes;
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 the output format ('overzicht met NHG- en niet-NHG-tarieven'), which adds some context, but lacks details on critical behaviors like data freshness, source reliability, rate limits, error handling, or authentication needs. For a data-fetching tool with zero annotation coverage, this is insufficient.

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 extremely concise and front-loaded: two sentences that directly state the purpose and output. There is no wasted text, repetition, or unnecessary elaboration. It efficiently communicates the essential information.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and output format, but lacks behavioral details (e.g., how current the rates are, any limitations). For a tool fetching financial data, more context on data currency and reliability would be beneficial, but it meets the basic threshold.

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 tool has 0 parameters, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so a baseline score of 4 is appropriate. It does mention the output includes NHG and non-NHG rates, which provides context on what data is returned.

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: 'Haalt actuele hypotheekrentes op per rentevaste periode' (Fetches current mortgage rates per fixed-rate period). It specifies the verb ('haalt op') and resource ('hypotheekrentes'), and distinguishes from siblings by focusing on rate retrieval rather than calculation or setup. However, it doesn't explicitly differentiate from potential similar rate-fetching tools that might exist elsewhere.

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 any of the sibling tools (e.g., bereken_hypotheek_* for calculations or opzet_hypotheek_* for setup), nor does it specify prerequisites, constraints, or scenarios where this tool is appropriate. Usage is implied only by the purpose statement.

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/pace8/mcp-hypotheken-berekenen'

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