Skip to main content
Glama

Alle Providers

Aansluitingen op een adres

aansluitingen
Read-onlyIdempotent

Which fixed connections reach a Dutch address: fiber, coax (cable) and copper (DSL), with the network owner, line speed and any network fee. Every listed connection is at the address. state "present" means the line is in the meter closet and can be ordered on; say so plainly, as the site does, and do not call it unconfirmed or unknown. Fiber can also be "connected", "planned", "in_street", "awaiting_connection" or "new_build". Use stateDescription and summary as given. Welke kabels er op een adres liggen, en of glasvezel aangesloten of gepland is.

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": "aansluitingen"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeYesDutch postcode, four digits and two letters, e.g. "1234AB" or "1234 AB".
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description does add real behavioral context beyond that: every returned connection is guaranteed to be at the address, and the state vocabulary (present, connected, planned, in_street, awaiting_connection, new_build) is disclosed along with an instruction to trust stateDescription/summary rather than reinterpret. It stops short of saying what an address with no connections returns.

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 what the tool returns, then the state semantics that matter most for correct reporting. The closing Dutch sentence largely restates the opening English one, which is mild redundancy, but no other sentence is wasted.

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 no output schema, the description carries the burden of describing returns and does so concretely: connection types, network owner, speed, fee, state values, and the authoritative stateDescription/summary fields. The main remaining gap is the empty-result case and whether results are paginated or always complete.

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?

Schema coverage is 100%, so the schema already documents postcode formatting, house number, and the toevoeging split rule. The description adds nothing parameter-specific, but the input contract is fully specified elsewhere; baseline 3 applies with a slight lift because the address-centric framing reinforces that all three parameters describe one location.

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 names a specific resource (fixed connections at a Dutch address) and enumerates exactly what comes back: fiber, coax, copper, plus network owner, line speed and network fee. It is unmistakably distinct in subject matter from the sibling search tools, though it never explicitly contrasts itself with them.

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 guidance is present but oriented toward interpretation rather than tool selection: it explains what 'present' means, warns not to relabel it as unconfirmed/unknown, and tells the agent to use stateDescription and summary verbatim. There is no statement of when to reach for this tool versus zoek_aanbod or zoek_gids, which an agent must infer from the address-based input.

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