Skip to main content
Glama

Alle Providers

Internetaanbod op een adres

zoek_aanbod
Read-onlyIdempotent

Find home internet offers (fiber, cable, DSL, 5G) at a Dutch address, with average monthly price, line speed, contract length and an order link. Zoekt het internetaanbod op een Nederlands adres. Een adres dat we deze week nog niet hebben gecheckt, kan tot ongeveer een minuut duren.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postcode": "<postcode>",
      "huisnummer": "<huisnummer>"
    },
    "name": "zoek_aanbod"
  }
}

Input Schema

NameRequiredDescriptionDefault
aantalNoNumber of offers (a provider can have one per connection type). Default 10.
pakketNoPackage: internet (default), internet-tv, internet-bellen (phone) or alles-in-een.
sorteerNoSort by prijs-per-mbit (value, default, as on the site), prijs (price) or snelheid (speed).
looptijdNoContract length in months: 1 (monthly cancellable), 12 or 24. Default 12.
postcodeYesDutch postcode, four digits and two letters, e.g. "1234AB" or "1234 AB".
techniekNoOnly this connection: glasvezel (fiber), coax (cable), koper (DSL) or draadloos.
max_prijsNoMaximum average price in euro per month.
huisnummerYesHouse number, e.g. 12. A suffix like "12A" or "12-2" is split into toevoeging.
toevoegingNoHouse number addition such as "A", "2" or "bis". Omit when there is none.
min_snelheidNoMinimum download speed in Mbit/s.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results include an order link, and an address not checked this week may take about a minute — a latency expectation an agent needs before calling.

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?

Front-loaded with the core capability in one dense sentence, then the latency caveat. The Dutch sentence largely restates the English one, so a portion of the text is duplication rather than added information.

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?

With ten parameters and no output schema, the description usefully names the returned fields and warns about slow responses. It omits edge cases such as no-offers-found behavior or result caps, but the essentials for a correct call are present.

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?

Schema description coverage is 100%, so every parameter (aantal, pakket, sorteer, looptijd, techniek, max_prijs, min_snelheid, toevoeging) is already documented with enums and defaults. The description only loosely maps connection types (fiber, cable, DSL, 5G) to the techniek enum, adding no syntax or default guidance beyond the schema.

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?

States a concrete verb and resource ('Find home internet offers') plus the address scope and connection types, and lists the fields returned (price, speed, contract length, order link). It never differentiates itself from the siblings zoek_gids or aansluitingen, so an agent gets a clear purpose but no explicit boundary.

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?

Usage is only implied by the domain: look up offers at a Dutch address. There is no statement of when to prefer this over zoek_gids/aansluitingen, no prerequisites, and no exclusions (e.g. non-Dutch addresses or unsupported connection types).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources