Skip to main content
Glama

Plekken in de buurt

plekken_in_de_buurt
Read-onlyIdempotent

Geeft de dichtstbijzijnde plekken van slimwegdoen.nl rond een plaats in Nederland, eventueel van één soort: kringloopwinkels, opkopers, repaircafés, weggeefplekken en goede doelen, of milieustraten. Met adres, afstand en of ze ophalen.

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": {
      "plaats": "<plaats>"
    },
    "name": "plekken_in_de_buurt"
  }
}

Input Schema

NameRequiredDescriptionDefault
soortNoWelk soort plek. Standaard alles.
plaatsYesWoonplaats, gemeente, postcode of adres in Nederland, bijvoorbeeld 'Amersfoort', '3811' of 'Stationsplein 1, Zwolle'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 adds real value beyond that: the data source (slimwegdoen.nl), the geographic scope (a location in the Netherlands), and the returned fields including whether a location offers pickup. It omits how many results come back or how 'nearest' is bounded, which is a minor gap for a lookup tool.

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?

A single front-loaded sentence leading with the verb and resource, followed by the optional filter and return fields. No filler, though the inline kind enumeration is dense and could be left to the schema.

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 only two parameters, full schema coverage, and rich annotations, the description covers what is missing structurally by naming the return fields (address, distance, pickup) in the absence of an output schema. Only the result-count/limit behavior is left unstated.

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 baseline is 3, but the description goes further by spelling out the concrete kinds behind the enum (kringloopwinkels, opkopers, repaircafés, weggeefplekken, goede doelen, milieustraten) and clarifying that 'plaats' is any Dutch place/address. It does not mention the 'bouwmateriaal' and 'alles' enum values, so the mapping is slightly incomplete.

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 specific verb and resource: it returns the nearest 'plekken' from slimwegdoen.nl around a Dutch location, optionally filtered by kind, with the data source and returned fields named. It is clear what the tool does, but it never names or contrasts the siblings (grofvuil_in_gemeente, waar_kan_dit_heen), leaving the agent to infer the boundary between searching for reuse/donation spots versus waste-disposal lookup.

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?

'Eventueel van één soort' implies how to narrow the search, so usage is implied rather than stated. There is no explicit when-to-use, when-not-to-use, or 'use X instead when…' guidance, which matters given two closely related siblings in the same waste-avoidance domain.

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