Skip to main content
Glama

haal_actuele_rentes_op

Retrieve current mortgage interest rates for different fixed-rate periods, showing both NHG and non-NHG rates for comparison.

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 'haal_actuele_rentes_op'. Extracts session ID, enforces rate limit if present, fetches current mortgage rates via GET to REPLIT_API_URL_RENTES using apiClient, and returns formatted JSON 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));
    }
  • Input schema definition for the tool: no required parameters, empty properties object.
      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: [],
      },
    },
  • src/index.ts:766-774 (registration)
    Registration of the tool handler in the TOOL_HANDLERS map, used by the CallToolRequestSchema handler to dispatch calls.
    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,
    };
  • Configuration constant for the Replit API endpoint URL used to fetch current 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. It mentions the output format ('overzicht met NHG- en niet-NHG-tarieven' - overview with NHG and non-NHG rates), which adds some behavioral context. However, it lacks details on rate limits, data sources, or potential errors, leaving gaps in transparency for a tool that fetches financial data.

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 purpose and output. There's no wasted text, though it could be slightly more structured by separating usage hints, but it's efficient for its length.

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 complexity (simple fetch operation with no parameters) and lack of annotations/output schema, the description is adequate but has gaps. It explains what is fetched and the output format, but doesn't cover behavioral aspects like data freshness or error handling, which could be important for financial data tools.

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%. The description doesn't need to add parameter details, as there are none. It provides context about what the tool fetches (mortgage rates per fixed-rate period with NHG/non-NHG breakdown), which is sufficient for a parameterless tool.

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 resource (mortgage rates) and verb (fetches), though it doesn't explicitly differentiate from sibling tools like 'bereken_hypotheek_doorstromer' (calculates mortgage for mover), which have different functions.

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 or contexts where this tool is preferred, such as for rate lookup versus mortgage calculation tools. Usage is implied by the purpose but not explicitly stated.

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/Test'

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